ORA-00257 archiver error. Connect internal only, until freed

ORA-00257 archiver error. Connect internal only, until freed.

Cause: The archiver process received an error while trying to archive a redolog. 
If the problem is not resolved soon, the database will stop executing transactions. 
The most likely cause of this message is the destination device is out of space 
to store the redo log file.

Action: Check the archiver trace file for a detailed description of the problem.
Also, verify that the device specified in the initialization parameter ARCHIVE_LOG_DEST is set up properly for archiving.

ORA-00257 comes under "Oracle Database Server Messages". 
These messages are generated by the Oracle database server when running any Oracle program.
How to free archive destination device:
Most probably archive destination is full. We should backup archive logs, then remove them.

We can use following steps for this
1. find the location of Archive destination by
SQL> ARCHIVE LOG LIST

Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            /u01/OracleHome/arch
Oldest online log sequence     11160
Next log sequence to archive   11163
Current log sequence           11163


2. move some files to some other location using os command
 cd /u01/OracleHome/arch
 mv /u01/OracleHome/arch/* /u01/OracleHome/archive_backup/
 

Or it can be done using RMAN also

rman target /

RMAN> backup archive log all format '/u01/OracleHome/archive_backup';

RMAN> delete archive until time 'trunc(sysdate)';

Comments

Node id does not exist for the current application server id

Issue: After completing cloning procedure, you generally may across the following issue. "Node id does not exist for the current application server id". Solution: First stop the application. Run adgendbc.sh script to configure apps tier dbc file with the correct id from the database instance. Start the application and test your issue. Location of script: 11i: $COMMON_TOP/admin/install/$CONTEXT_NAME R12: $INST_TOP/admin/install [appldev@erptest install]$ sh adgendbc.sh (Note: It will prompt you to give apps username and apps password.)

How to change EBS R12 database and application port number

On Database Tier 1. Logon as oracle database user and source environment for R12 RDBMS ORACLE_HOME 2. Start database instance for which you want to change R12 port 3. Backup contextfile 4. Change as below in contextfile dbport : Change database port from 1521 to 1541 db_ons_localport : 6300 to 6320 db_ons_remoteport : 6400 to 6420 cmanport : 1521 to 1541 5. Run adautocfg.sh On Apps Tier Change Application port from 8000 to 8020 1. Logon as application manager user and source environment for R12 2. Backup contextfile 3. Run adpreclone $ perl ./adpreclone.pl appsTier 4. Run adcfgclone and choose new port pool $ cd $COMMON_TOP/clone/bin $ perl ./adcfgclone.pl appsTier 5. Check new application URL SQL> select home_url from icx_parameters; HOME_URL ----------...

Oracle R12 : You are trying to access a page that is no longer active

Login fails “You are trying to access a page that is no longer active.” The issue can be reproduced at will with the following steps: Issue : After cloning process the login page of Oracle E-Business Suite R12 show the above error. Solution : For this you need to update the new hostname in the icx_parameteres table 1. SQL> SELECT SESSION_COOKIE_DOMAIN FROM icx_parameters; SESSION_COOKIE_DOMAIN --------------------- erp.local.com (This is hostname of Source Application Tier) 2. SQL>update icx_parameters set SESSION_COOKIE_DOMAIN = ‘target.local.com’; 1 row updated. SQL> commit; Commit complete. (This has changed the SESSION_COOKIE_DOMAIN of target application to target hostname.domain_name) 3. SQL> SELECT SESSION_COOKIE_DOMAIN FROM icx_parameters; SESSION_COOKIE_DOMAIN --------------------- target.local.com

Latest Technology Blog

Search This Blog