Archive for August, 2019

Enable Pluggable Database(PDB) Archivelog Mode

August 26th, 2019, posted in Oracle Queries
Share

Enabling archive log mode -12c pluggable database/Container database

Since the Redologs are created at container database level in 12c and not at pluggable database level.
(Enabling archivelog at pluggable database level is not possible). Archiving is done at CDB’s.

You can check archive log mode either by querying v$database or archive-log list :

 

SQL> select name,open_mode,log_mode from v$database;

NAME      OPEN_MODE            LOG_MODE
--------- -------------------- ------------
CDB      READ WRITE           NOARCHIVELOG

(OR)

SQL> archive log list
Database log mode        Archive Mode
Automatic archival        Disabled
Archive destination        USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     11
Next log sequence to archive   13
Current log sequence        13

***************  ***************
To enable the Archive-log mode
***************  ***************immam_dba,dba immam,imam dba,dba imam,oracle clone issue,oracle database,oracle application,oracle clone issue,ora oracle

SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.

SQL> startup mount;
ORACLE instance started.

Total System Global Area  788529152 bytes
Fixed Size      2929352 bytes
Variable Size    541068600 bytes
Database Buffers   239075328 bytes
Redo Buffers      5455872 bytes
Database mounted.

SQL> ALTER DATABASE ARCHIVELOG;
Database altered.

SQL> ALTER DATABASE OPEN;
Database altered.

SQL> select name,open_mode,log_mode from v$database;

NAME      OPEN_MODE            LOG_MODE
--------- -------------------- ------------
CDB      READ WRITE           ARCHIVELOG



SQL> archive log list
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     413
Next log sequence to archive   415
Current log sequence           415

SQL> show parameter DB_RECOVERY_FILE_DEST

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest                string      /u03/app/oracle/fast_recovery_area
db_recovery_file_dest_size           big integer 27G

 

Share

Treat The Members Of Your Family With Love And Respect

August 22nd, 2019, posted in Saying Of Hazrat Ali ( A.S )
Share

Treat The Members Of Your Family With Love And Respect

Share

Fear Allah in Matters Concerning Orphans

August 15th, 2019, posted in Saying Of Hazrat Ali ( A.S )
Share

By Imam Ali, Will By Imam Ali, Hazrat Ali, Imam Ali, islam, islamic Quote, islamic Quote Saying, islamic Quotes, islamic Quotes Sayings, islamic Saying, islamic Sayings, islamic teaching, islamic teachings, Saying.jpg, sayings, Sayings of Hazrat Ali, sayings of Imam Ali,Last Will Of Hazrat Ali

Share

Apache HTTP_Server – Failed to start a managed process after the maximum retry limit Log (HTTP_Server~1)

August 12th, 2019, posted in Oracle
Share

Oracle HTTP Server, residing on a Unix platform, fails to start using OPMN. For example, OPMN reports the generic error

 

opmnctl startall
opmnctl: starting opmn and all managed processes...
================================================================================
opmn id=oradb:6200
0 of 1 processes started.

ias-instance id=infra.oracle.com
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ias-component/process-type/process-set:
HTTP_Server/HTTP_Server/HTTP_Server

Error
--> Process (pid=24042)
Failed to start a managed process after the maximum retry limit Log::
/opt/oracle/infra/opmn/logs/HTTP_Server~1

The HTTP_Server~1 OPMN log file just reports that the HTTP Server has been started, but there are actually no httpd processes present on the system.

There is also nothing written to the $ORACLE_HOME/apache/apache/logs directory even when HTTP Server logLevel is set to debug.

Furthermore there are no core / segmentation fault files created.

In order for the HTTP Server to listen on ports < 1024 e.g 80 and 443 the ownership and permissions of the Oracle HTTP Server binary – ‘.apachectl’ – have been changed as follows:

One possible work-around is to change .apachectl to belong to another group – such as the generic one users (rather than have the file belong to the oracle group – typically called ‘oinstall’) e.g

 

Solution:

chown root:users .apachectl
chmod 6750 .apachectl
Share