WebLogic Admin Server Fails to Start with Error "JPS-02592: Failed to push ldap config data to libOvd for service instance

 

Unable to start Admin server in WCP domain.  Log file shows the following error message:

 

Jun 18, 2016 4:30:21 PM oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider pushLdapNamesTolibOvd
SEVERE: JPS-02592
<Jun 18, 2016 4:30:21 PM PDT> <Error> <Security> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context "default", cause: org.xml.sax.SAXParseException: <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.>
<Jun 18, 2016 4:30:21 PM PDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context "default", cause: org.xml.sax.SAXParseException: <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context "default", cause: org.xml.sax.SAXParseException: <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.

CHANGES

 

CAUSE

The adapters.os_xml file is empty.

SOLUTION

1) Take a backup of $DOMAIN_HOME/config/fmwconfig/ovd/default/adapters.os_xml 

2) Delete corrupted adapters.os_xml 

3) Copy adapters.os_xml from $MW_HOME/oracle_common/modules/oracle.ovd_11.1.1/templates/ to $DOMAIN_HOME/config/fmwconfig/ovd/default/

4) Restart the server.

Reference Oracle Doc: (Doc ID 2151498.1)

RFS[2]: No standby redo logfiles available for T-1

 Error Reason: Redo Log size different in Primary and Standby Database.

Solution:

---------Standby Database--------
SQL> alter database recover managed standby database cancel;

Database altered.

SQL> alter system set standby_file_management=manual;

System altered.

SQL> alter database drop STANDBY logfile group 61;

Database altered.

SQL> alter database drop STANDBY logfile group 62;

Database altered.

SQL> alter database drop STANDBY logfile group 63;

Database altered.

SQL> alter database drop STANDBY logfile group 64;

Database altered.

SQL> alter database drop STANDBY logfile group 65;

Database altered.

SQL> alter database drop STANDBY logfile group 66;

Database altered.

SQL>
SQL> select group# from v$standby_log;

no rows selected

SQL> ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 61 ('+REDO1','+REDO2','+REDO3') size 1024M;

Database altered.

SQL> ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 62 ('+REDO1','+REDO2','+REDO3') size 1024M;

Database altered.

SQL> ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 63 ('+REDO1','+REDO2','+REDO3') size 1024M;

Database altered.

SQL> ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 64 ('+REDO1','+REDO2','+REDO3') size 1024M;

Database altered.

SQL> ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 65 ('+REDO1','+REDO2','+REDO3') size 1024M;

Database altered.

SQL> ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 66 ('+REDO1','+REDO2','+REDO3') size 1024M;

Database altered.

SQL> alter system set standby_file_management=auto;

System altered.

SQL> recover managed standby database using current logfile disconnect;
Media recovery complete.
SQL>
SQL>
SQL>

Too many arguments passed in(2023). Limit is 2000 in Apex

Error:

Too many arguments passed in(2023). Limit is 2000


Solution:

Add the marked line in plsql.conf file and then restart ohs service

[root@IOFFSHORE ohs1]# vim /u01/oracle/middleware/asinst_1/config/OHS/ohs1/moduleconf/plsql.conf

PlsqlLogEnable On

PlsqlLogDirectory "${ORACLE_INSTANCE}/diagnostics/logs/${COMPONENT_TYPE}/${COMPONENT_NAME}"

# PlsqlIdleSessionCleanupInterval 15 (default)

# PlsqlDMSEnable On (default)
PlsqlMaxParameters 4000

# ============================================================================
# Database Access Descriptors Settings Section
# ============================================================================
include "${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/mod_plsql/dads.conf"


-------Now restart the ohs1 component-----

[root@IOFFSHORE ohs1]# cd /u01/oracle/middleware/asinst_1/bin/
[root@IOFFSHORE bin]# ./opmnctl stopall
opmnctl stopall: stopping opmn and all managed processes...
[root@IOFFSHORE bin]# ./opmnctl startall
opmnctl startall: starting opmn and all managed processes...
================================================================================
opmn id=IOFFSHORE:6701
Response: 2 of 3 processes started.

ias-instance id=asinst_1
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ias-component/process-type/process-set:
  emagent_asinst_1/EMAGENT/EMAGENT/

Error
--> Process (index=1,uid=2072455298,pid=91782)
  failed to start a managed process after the maximum retry limit
  Log:
  /u01/oracle/middleware/asinst_1/diagnostics/logs/EMAGENT/emagent_asinst_1/console~EMAGENT~1.log

[root@IOFFSHORE bin]# ./opmnctl status

Processes in Instance: asinst_1
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status
---------------------------------+--------------------+---------+---------
emagent_asinst_1                 | EMAGENT            |     N/A | Down
RptSvr_IOFFSHORE_asinst_1        | ReportsServerComp~ |   91568 | Alive
forms                            | FormsRuntime       |   91406 | Alive
forms                            | FormsRuntime       |   91225 | Alive
forms                            | FormsRuntime       |   84824 | Alive
ohs1                             | OHS                |   91566 | Alive

[root@IOFFSHORE bin]#