When we’re trying to post the data using REST service after we add some parameter in existing package, we’re getting the error while post
“Message”: “Error while executing service”,
“Resolution”: “System error, please see service log trace for details”,
Log in error while deploy REST service
PLS-00306: wrong number or types of arguments in call to ‘HAS_DEFAULT’
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
Functional Administrator –> clear cache
undeploy and deploy the service again
Now we can able to post data
When i am trying to access the weblogic server console from one of client machine, I am getting the below error
If you have applied the Critical Patch Update (CPU) released in April 2019, then you can use the context variable
s_wls_admin_console_access_nodes to specify the trusted hosts used by administrators that require access to the Oracle WebLogic Server Administration Console and Fusion Middleware Control. Set this context variable to a list of trusted hosts that are allowed to access the consoles using the Oracle WebLogic Server Administration ports.
Run file system, we need to add the client ip or hostname lists in context file
stop and start service
Now we can able to reach the weblogic server console URL
SELECT d.employee_number EMPLOYEE_ID,d.full_name EMPLOYEE_NAME,a.USER_NAME USERID,e.name POSITION,frv.responsibility_name RESPONSIBILITIES_ASSIGNED,
FROM apps.fnd_responsibility_vl frv,apps.FND_USER a,apps.FND_USER_RESP_GROUPS_all b,apps. per_all_people_f d,apps.FND_RESPONSIBILITY_TL res,PER_JOBS_VL e,
b.responsibility_id = res.responsibility_id
and a.USER_ID=b.USER_ID and b.RESPONSIBILITY_ID=frv.RESPONSIBILITY_ID and a.employee_id=d.person_id
and sysdate between d.effective_start_date and d.effective_end_Date
and sysdate between nvl(frv.start_date,sysdate) and nvl(frv.end_date,sysdate)
AND f.job_id = e.job_id
group by d.employee_number,a.USER_NAME,frv.responsibility_name, d.full_name,b.START_DATE,b.end_date,decode(a.END_DATE,NULL,’ACTIVE’,’INACTIVE’),
ORDER BY d.full_name
I upgraded EBS Version from 12.1.3 to 12.2.9. After upgraded, i planned to setup the Java webstart for EBS 12.2.9 version. As such, i review the document (Doc ID 2188898.1), this document clearly explained about how to setup the java webstart on EBS.
There was many patches noted to apply on EBS version for java webstart. But my case, I have already upgraded to latest version. so all the patches are included whichever required.
Section : 4.2.2 Oracle Forms 10g Technology Patch for Oracle E-Business Suite Release 12.2
the document noted to apply the patch Patch 25441839 but Patch 26825525 already applied during upgrade activity. so no need to apply the patch 25441839 (Doc ID 2554599.1).
you need to follow further steps for Java webstart setup.
When i trying to undeploy the REST service in UAT and deploy again, i am getting the below error.
java.lang.SecurityException: User: ASADMIN authentication failed
verify the asadmin given credential correct and roles also.
Run the txkISGConfigurator.xml utility with “ebsSetup” argument.
ant -f $JAVA_TOP/oracle/apps/fnd/txk/util/txkISGConfigurator.xml ebsSetup -DforceStop=yes -DforceDataSourceExists=true -DforceAuthenticationProviderExists=true
refer : Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12.2 (Doc ID 1311068.1)
Section 2: Configuring Oracle E-Business Suite Integrated SOA Gateway for REST Services
I am trying to logging in sysadmin user of one of our UAT system, It’s simply loading but not logging in.
I checked the sysadmin user credentials valid. Yes it’s Valid.
select fnd_web_sec.validate_login(‘SYSADMIN’,’password’) from dual;
I checked any blocking session in database, Yes it’s there . So I kill those sessions afterwards I can able to login.
select l1.sid, ‘ IS BLOCKING ‘, l2.sid
from v$lock l1, v$lock l2 where l1.block =1 and l2.request > 0
and l1.id1=l2.id1 and l1.id2=l2.id2
Suddenly We couldn’t able to save the file after we did export.
Check your database any one of tablespace space issue in alert log file and add datafile.