SQL to Check Physical Standby in Sync with the Primary

On Primary database:

SELECT distinct SEQUENCE# "Last Sequence Generated", THREAD# "Thread"
FROM V$ARCHIVED_LOG
WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)
ORDER BY 1;

On Standby database:

SELECT ARCH.THREAD# "Thread", 
       ARCH.SEQUENCE# "Last Sequence Received", 
       APPL.SEQUENCE# "Last Sequence Applied", 
       (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference"
FROM
(SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,
(SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL
WHERE ARCH.THREAD# = APPL.THREAD#;
www.pdf24.org    Send article as PDF   
Posted in My Reference | Tagged , | Leave a comment

Configuring Wallet Manager to enable HTTPS connect with Oracle 12c database

The newer post regarding to this topic other than two ones for oracle 10g and 11g. Once we got database upgraded to 12c, issue was reported by users and we got error below when we checked it.

SQL>  select utl_http.request('https://secure.aizan.biz/Web/Common/XmlAutomation/Upload.aspx', null, 'file:/oracle/wallet','doug1las') from dual;
 select utl_http.request('https://secure.aizan.biz/Web/Common/XmlAutomation/Upload.aspx', null, 'file:/oracle/wallet','xxxxxxxx') from dual
        *
ERROR at line 1:
ORA-29273: HTTP request failed
ORA-29024: Certificate validation failure
ORA-06512: at "SYS.UTL_HTTP", line 1491
ORA-06512: at line 1

I then tried to re-import the certificate. However, the following error returned.

Oracle_Wallet_Import_CertificateMy next tryout is to recreate the wallet and re-import the certificate. Unfortunately, different error returned.

SQL>  select utl_http.request('https://secure.aizan.biz/Web/Common/XmlAutomation/Upload.aspx', null, 'file:/oracle/wallet','doug1las') from dual;
 select utl_http.request('https://secure.aizan.biz/Web/Common/XmlAutomation/Upload.aspx', null, 'file:/oracle/wallet','xxxxxxxx') from dual
        *
ERROR at line 1:
ORA-29273: HTTP request failed
ORA-28759: failure to open file
ORA-06512: at "SYS.UTL_HTTP", line 1491
ORA-06512: at line 1

My solution is to change attributes of wallet directory /oracle/wallet to 777 instead of 755.

To solve the original error, I tried to generate certificate in format “Base-64 encoded X.509 (.CER)” instead of below .P7B one. And then, re-creating wallet and importing this certificate solved the problem.

I guess oracle 12c requires more secure certificate than previous versions.

Generate_Certificate_Base-64 encoded X.509

 

en.pdf24.org    Send article as PDF   
Posted in Oracle Case Study, Oracle Point | Tagged , , | Leave a comment

Failed to log in OEM Cloud Control with Correct Username (sysman) and Password

In the past years, I experienced the log in issue with Oracle Enterprise Manager Cloud Control couple of times. For sure I went with correct user name (sysman) with correct password, but still get error message below.

“Authentication failed. If problem persists, contact your system administrator”

The default admin user of OEM Cloud Control is sysman, which is user of OEM repository database. Just simply log in to database as sysman with password via sql*plus, you’ll know if username and password are correct. In my case, I can log in to database via sql*plus with no issue. That meant the password to sysman is correct.

Oracle article DOC ID 1493151.1,“EM 12c, EM 13c: Login to Enterprise Manager Cloud Control with the Correct Password Fails with Error: Authentication failed. If problem persists, contact your system administrator” gives SYMPTOMS,CAUSE, and SOLUTION.

SYMPTOMS:

Error logged in the <gc_inst>/em/EMGC_OMS1/sysman/log/emoms.trc file:

2012-09-21 10:26:14,290 [[ACTIVE] ExecuteThread: ‘5’ for queue: ‘weblogic.kernel.Default (self-tuning)’] ERROR audit.AuditLogHandler auditLog.381 – Could not log the audit record java.sql.SQLException: ORA-14400: inserted partition key does not map to any partition
ORA-06512: at “SYSMAN.MGMT_AUDIT”, line 873
ORA-06512: at “SYSMAN.MGMT_AUDIT”, line 402
ORA-06512: at line 1

OR

2013-12-17 12:24:49,205 [[ACTIVE] ExecuteThread: ‘0’ for queue: ‘weblogic.kernel.Default (self-tuning)’] DEBUG auth.EMLoginService _performLogin.825 – Error
java.sql.SQLException: ORA-04063: package body “SYSMAN.MGMT_AUDIT_ADMIN” has errors
ORA-06508: PL/SQL: could not find program unit being called: “SYSMAN.MGMT_AUDIT_ADMIN”
ORA-06512: at “SYSMAN.MGMT_AUDIT”, line 143
ORA-06512: at “SYSMAN.EM_USER_MODEL_UI”, line 1521
ORA-04063: package body “SYSMAN.MGMT_AUDIT_ADMIN” has errors
ORA-06508: PL/SQL: could not find program unit being called: “SYSMAN.MGMT_AUDIT_ADMIN”
ORA-06512: at line 1

CAUSE:

The console login creates an audit entry in the EM related audit table. If this audit entry is not successful for some reason, then the console login will fail.

Case 1:

Issue was investigated in the below bugs:

Bug 14285322: GC12:VALUE FOR JOB_QUEUE_PROCESSES SHOULD NOT BE ZERO AFTER UPGRADE
BUG 16205038 : [EMCC] DBMS JOBS ARE NOT EXECUTED REGULARLY CAUSING AUTHENTICATION FAILURE

It was identified that a recent upgrade / maintenance activity (for example: patching or plugin upgrade) was performed on the setup, which had set the job_queue_processes initialization parameter to 0 in the EM repository database. This had prevent the execution of the DBMS_JOBS responsible for maintenance of the repository. Console login needs to create an entry into the Audit tables but the necessary partitions had not been created for this table.

Case 2:

There is resource issue at the repository database, for example ORA-4031 or ORA-01658 due to insert into the the audit table fails.

Case 3:

The Audit related objects were invalid in the repository database.

SOLUTION:

Our issue is Case 1.

If an upgrade / maintenance activity (for example: patching or plugin upgrade) was performed recently, the job_queue_processes initialization parameter could be still set to 0 and not reset to the original value. This would prevent the DBMS Scheduler jobs related to the repository from getting executed correctly due to which the new partitions for the Audit tables entries are not created.

1. Login to the database as a SYSDBA user and set the job_queue_processes initialization parameter to a value of 20:

SQL> ALTER SYSTEM SET job_queue_processes=20 SCOPE=BOTH SID=’*’;

2. If the job_queue_processes value is already set, verify that this set to 20 or more.
    Verify that the DBMS scheduler jobs of the repository are running fine using the steps in:

Note 1470166.1 : 12c DBMS Jobs in Invalid Schedule Status in the Console Page

3. Execute the following queries in repository DB as SYSMAN user:

SQL> update mgmt_audit_master set prepopulate_days=5 where prepopulate_days is null;
SQL> exec mgmt_audit_admin.add_audit_partition;

4. Restart the OMS:

cd <OMS_HOME>/bin
./emctl stop oms -all
./emctl start oms

Note: After I figured out this issue the first time I experienced, I just simply run command exec mgmt_audit_admin.add_audit_partition; when it happened again.

PDF24    Send article as PDF   
Posted in My Reference | Tagged , | 1 Comment

Protected: Ellucian Identity Service (Part 7)-Banner 8 INB/SSB Single SIgn On with BEIS SSO Manager

This content is password protected. To view it please enter your password below:

PDF24    Send article as PDF   
Posted in Ellucian | Tagged , , | Enter your password to view comments.

Protected: Ellucian Identify Service (Part 6)–Banner XE Configuration for Single Sign On with EIS

This content is password protected. To view it please enter your password below:

www.pdf24.org    Send article as PDF   
Posted in Ellucian | Tagged , | Enter your password to view comments.