ORA-16047 When Starting Active DG

This past night I have been activating an active dg. The issue is that it did not finish to start and at the beginning it gave the following error;

ORA-16047: DGID mismatch between destination setting and target database

Looking more in detail at the specific trace file, the following message appears (this is an excerpt of the file);

2018-07-31 07:17:27.263: [ GPNP]clsgpnpkwf_initwfloc: [at clsgpnpkwf.c:471] Result: (7) CLSGPNP_IO. (:GPNP01002:)Failed to open wallet file. dir ‘peer’ in ‘/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/wallets/’, cannot check wallet home.
2018-07-31 07:17:27.263: [ GPNP]clsgpnpkwf_initwfloc: [at clsgpnpkwf.c:469] (:GPNP01002:)SlfFopen2
Internal Error Information:
Category: SLF_SYSTEM(-8)
Operation: lstat failed
Location: slsfopen3
Other:
Dep: 13
Dep Message: Permission denied

In this case the error is caused by the fact that the log_archive_config parameter is not configured. You can query the value of this parameter in the next way;

show parameter log_archive_config

And you can set it by use the next alter command;

alter system set LOG_ARCHIVE_CONFIG=’DG_CONFIG=(db,stbdb)’;

HTH – Antonio NAVARRO

 

 

 

 

Advertisements

Release 18C released

Oracle has just released version 18c “on-premise”, now all the politics is the cloud and they are putting names for the versions that are not for the cloud.

Indicate that the version has only been released for Linux, also an Oracle policy change that has traditionally made the first versions for Solaris. Which seems to confirm the rumors that Solaris ends in 2030 😦

 
I attached the link for download;

Oracle Database 18.3

And a couple of screenshots

photo_db_18c_v1

photo_db_18c_v2

HTH – Antonio NAVARRO

Killing Session With post_transaction Clause

Today I would like to talk about the option to kill a connection with the post_transaction clause, it looks like the shutdown transactionl that the database has. In this case you wait for the process to finish its work.

  • The POST_TRANSACTION setting allows ongoing transactions to complete before the session is disconnected.
  • If the session has no ongoing transactions, then this clause has the same effect described for the KILL SESSION.

An example would be the following;

ALTER SYSTEM DISCONNECT SESSION ‘sid, serial #’ POST_TRANSACTION

HTH – Antonio NAVARRO