Category: Oracle

Error 1033 received logging on to the standby

PRIMARY:

alert.log:

Error 1033 received logging on to the standby
Wed Jul 10 16:15:08 2019
Error 1033 received logging on to the standby
Wed Jul 10 16:16:11 2019
Error 1033 received logging on to the standby
Wed Jul 10 16:17:13 2019
Error 1033 received logging on to the standby

dr.log:

07/10/2019 16:19:57
Failed to connect to remote database TESTSTY. Error is ORA-01033
Failed to send message to site TESTSTY. Error code is ORA-01033.
Data Guard Broker Status Summary:
Type Name Severity Status
Configuration TESTDB Warning ORA-16607
Primary Database TESTDB Error ORA-16778
Physical Standby Database TESTSTY Error ORA-01033

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe

ORA-16665: timeout waiting for the result from a database

$ oerr ora 16665
16665, 0000, "timeout waiting for the result from a database"
// *Cause: The Oracle Data Guard broker was forced to time out a network
// connection to a remote database because:
// - The network call to the remote database did not complete in
// a timely manner.
// - The remote database was unable to execute the command due to
// an instance failure.
// *Action: Check Data Guard broker log files for the details of the failure.
// If the network call did not complete in a timely manner, increase
// the CommunicationTimeout configuration property value and reissue
// the command.

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe

Create Materialised View Log on the Remote Database

DB1 is a local database, on which the materialized views are to be created.
DB2 is a remote database, on which materialized view logs are created .

The high level steps are:

  • on local database DB1, create a database link between DB1 and DB2 database.
  • On the remote database DB2, create materialized logs on the tables of DB2.
  • On local database DB1, create materialized views with Fast Refresh option , etc.
  • On Local database DB1, run a complete refresh on your materialized views:          Exec dbms_snapshot.refresh(‘schema_name.mview_name’,’c’);
  • Then on local database DB1 again ,  refresh the materialized  view using the Fast Refresh option:
    Exec dbms_snapshot.refresh(‘schema_name.mview_name’,’f’);

ORA-02800: Requests timed out from Oracle Scheduler Job

Get errors from running an Oracle scheduler job:

SQL> exec dbms_scheduler.run_job(job_name=>'BATCH_JOB', 
                                 use_current_session=>false);
BEGIN dbms_scheduler.run_job(job_name=>'BATCH_JOB', 
                                 use_current_session=>false); END;

*
ERROR at line 1:
ORA-02800: Requests timed out
ORA-06512: at "SYS.DBMS_ISCHED", line 196
ORA-06512: at "SYS.DBMS_SCHEDULER", line 486
ORA-06512: at line 1

WORKAROUND

1)check parameter to make sure not zero.

SQL> show parameter job_queue_processes

NAME                                 TYPE     VALUE
-------------------------------- ------------ ------------------
job_queue_processes                integer    100

2) Bounce the database due to the bugs.

3) Rerun the job successfully.

SQL> exec dbms_scheduler.run_job(job_name=>'BATCH_JOB', 
use_current_session=>false);

PL/SQL procedure successfully completed.

ORA-29283: invalid file operation ORA-06512: at “SYS.UTL_FILE”, line 536 ORA-29283: invalid file operation

Connected to Oracle database through service name, then get  errors by running the below sample code.  There is no problem to run the sample code while connecting to database through IPC.

$sqlplus testuser/****@DBTEST

SQL>DECLARE
    l_output utl_file.file_type;
BEGIN
    l_output := utl_file.fopen( 'MY_DIR', 'test.txt', 'w' );
    utl_file.fclose( l_output ); 
END;
/

*
ERROR at line 1:
ORA-29283: invalid file operation
ORA-06512: at "SYS.UTL_FILE", line 536
ORA-29283: invalid file operation
ORA-06512: at line 4
$sqlplus  / as sysdba
SQL> DECLARE
     l_output utl_file.file_type;
BEGIN
     l_output := utl_file.fopen( 'MY_DIR', 'test.txt', 'w' );
     utl_file.fclose( l_output );
END;

 /

PL/SQL procedure successfully completed.

CAUSES

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe