RMAN alert log Message: ALTER SYSTEM ARCHIVE LOG

Similar Questions

• When ALTER SYSTEM ARCHIVE LOG happens implicitly...

  Hello
  
  When you scan the v$ archived_log SIDE primary SCHOOL, I saw below output
  
  NAME OF CREATOR REGISTR SEQUENCE # FAL
  -------------------------- ------- ------------ ----------------- ---
  /U05/prod/archivelogs/ARC_816992406_1_22885.dbf ARCH ARCH 22885 No.
  /U05/prod/archivelogs/ARC_816992406_1_22886.dbf FGRD FGRD 22886 No.
  
  
  Then I went to the alert log file and search for the sequence #, I found that
  
  When the newspaper switch happens through * ALTER SYSTEM ARCHIVE LOG *, then this sequence archive log CREATOR and REGISTRAR will be FGRD.
  What command of newspaper happens automatically (90% complete log file), then this sequence archive log CREATOR and REGISTRAR will be ARCH.
  
  
  If * ALTER SYSTEM ARCHIVE LOG * happens synchronously means control will not return to the process unless and until the underlying log file has been
  archived completely, so the CREATOR and the REGISTRAR is FGRD.
  
  My question is, under what circumstances * ALTER SYSTEM ARCHIVE LOG * happen implicitly.
  
  
  Thank you

  Hello

  user9085814 wrote:
  Thanks for the reply...

  I agree with you.

  The environment that I take abt is DATAGUARD Enviornment.

  I have not published ALTER SYSTEM ARCHIVE LOG CURRENT of any session (foreground process) of the primary DB.
  But I can still see ALTER SYSTEM ARCHIVE LOG in the log to alter.

  When you call the command ALTER SYSTEM ARCHIVE LOG CURRENT , then oracle write in the journal of the alerts as:

  On primary

  
   Wed May 15 09:16:56 2013
   Archived Log entry 789 added for thread 1 sequence 396 ID 0xf23a6e3f dest 1:
   *ALTER SYSTEM ARCHIVE LOG*
   Thread 1 cannot allocate new log, sequence 398
  

  >

  So my question on what scenario ALTER SYSTEM ARCHIVE LOG will be captured in the log of alerts.
  because it's a mistake to run foreground process ALTER SYSTEM ARCHIVE LOG .

  Have you had a logs archived backup RMAN script which is called ALTER SYSTEM ARCHIVE LOG CURRENT

   RMAN> run
             {
                sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
                backup  archivelog all delete all input;
             }
  

  If you try the command ALTER SYSTEM ARCHIVE LOG CURRENT on stanby, you get error ORA-01109: database is not open. This means database is not open READ/WRITE mode.
  Then we can use ALTER SYSTEM ARCHIVE LOG CURRENT on the standby database.

  Thanks for the interesting thread
  Mr. Mahir Quluzade
  http://www.Mahir-quluzade.com

• Errors in archiving in the alerts log

  Hello
  
  I have an Oracle Database 9i (9.2.0.7) for which I shot on the mode of arhivelog a week ago. In this PB in the alerts log there following errors:
  
  Arc1: Evaluating archive log 1 thread 1 sequence 1221
  Arc1: Impossible to archive log 1-wire 1 sequence 1221
  Newspapers archived by another process
  Arc1: Evaluating archive log 2 thread 1 sequence 1222
  Arc1: Impossible to archive log 2 thread 1 sequence 1222
  Newspapers archived by another process
  
  and there is no message like "Archiving completed" because of another problem - there was a mistake in specifying the format of newspaper. The of log_archive_format is incorrectly set to 'DB001_%s_%t_%r.arc' so also there is another trace file that says that:
  
  SESSION ID: (9.1) 2009-03-11 08:42:00.023
  ORA-00294: format specifier invalid archivelog 'r '.
  
  (There are two things: 1) to change the format of journal archive
  (2) to deal with the other issue: impossible to archive log 2 thread 1 sequence 1222
  Newspapers archived by another process
  
  What is the process to do this? Will be grateful for the help. The database is now.
  
  Thank you
  Cedric
  
  Published by: orausern on May 1st, 2009 01:14

  orausern wrote:
  Thanks for the suggestion, I tried it, but it gives an error like:
  ERROR on line 1:
  ORA-02095: specified initialization parameter is not editable

  In addition to the parameter log_archive_format isn't editable session or system. My concern is that since this error is over a week old, it will allow me to close the db itself (when I get the permission to do so), or there will be a problem if I try to close the db, then restart. so I do not know how...

  Thank you
  Cedric

  I guess you took bad, this setting can be changed indeed but the effect of this would come at the next startup only one, this is a static setting.

  http://download.Oracle.com/docs/CD/B10501_01/server.920/a96536/CH195.htm#REFRN10089

  If you need to do something like that,

  alter system set log_archive_format= scope=spfile;
  

  Do a reset and setting of parameters entered into force. No matter what dba account must be able to change this setting, but for the bounce of the db, you must have Sysdba privileges. This setting won't make your startup or a stop, they should go ahead without problem.

  HTH
  Aman...

• CREATE/ALTER/DROP instructions and alerts log

  In the Oracle (12 c) Administrator's Guide under "monitoring errors with Trace files and alert newspaper ' is the following:

  Alerts log is a chronological record of the messages and errors, and includes the following items:

  -Any internal (ORA-00600), errors (ORA-01578) block and corruption blocking errors (ORA-00060) that occur

  - Administrative, operations such as CREATE, ALTER, and DROP statements and instructions STARTUP, SHUTDOWN and ARCHIVELOG

  -Messages and shared server process and dispatcher functions errors

  -The errors that occur when automatic refreshing a materialized view

  -The values of all initialization parameters that have default values at the time where the departure of the database and instance

  My question is about the second point (in bold).  I might be accused of not followed my journal to alert as closely as I should, but I have not noticed the CREATE/ALTER/DROP instructions in there.  I went to one of my test cases and created a table. No message was written for the journal of alerts.  I did a logfile switch just to make sure I was looking at the right file.  Yep - the switch is in the newspaper.  I dropped my test table - once again, no alert log entry was created.

  So my question is if the above is a documentation error or am miss me a piece of the puzzle?

  Hello

  It would really help if you posted a link to the document you are referencing, such as

  http://docs.Oracle.com/CD/B28359_01/server.111/b28310/monitoring001.htm#ADMIN11242

  The ball before the one you pointed out said «All the internal errors...» »

  The ball that you pointed out does not say "All", so I interpret that as meaning only some of the most remarkable commands CREATE, ALTER, and DROP are recorded, for example CREATE TABLESPACE or ALTER SYSTEM.

  Like you, I think that literature should be clearer on this point.

  Below is the article you cited, there is a link:

  http://docs.Oracle.com/CD/B28359_01/server.111/b28310/diag001.htm#CHDHEGBH

  which goes into a little more detail on this stuff is saved.  They are mostly all systemically important things, not things like creating a package, or editing a table individual users.  When the part you highlighted speaks of 'administrative operations, such as CREATE, ALTER, and DROP statements ', I think they're trying to distinguish certain types of CREATE, ALTER, and DROP statements, for example, things that only highly privileged users such as SYS or SYSTEM can do other, more frequent, CREATE, ALTER, and DROP statements.  Again, this is largely what I read in the literature, based on my experience.  Would be nice if the documentation is more explicit on this subject.

• Archiving RMAN error logs

  Hi all. I have a problem to make my first backup. I created the recovery catalog database, saved the database target with catalogue, modified the database log mode to achieve and started the following with the error script.
  
  MAN & gt; Run {}
  2 & gt; allocate channel c1 type disk;
  3 & gt; backup of database format "db_ u_ % d_ %s % ';
  4 & gt; backup format 'log_t % t_s %%p s_p ".
  5 & gt; ( archivelog all );
  6 & gt; }
  
  allocated channel: c1
  channel c1: sid = 365 devtype = DISK
  From backup to 24-SEP-08
  channel c1: from full datafile backupset
  
  channel c1: specifying datafile (s) in backupset
  input datafile fno = name=/oradata/mybd/others01.dbf 00010
  input datafile fno = 00001 name=/oradata/mybd/system01.dbf
  input datafile fno = name=/oradata/mybd/sysaux01.dbf 00003
  channel c1: starting piece 1 to 24 - SEP-08
  channel c1: finished piece 1 to 24 - SEP-08
  piece handle=/oracle/10.2.0/dbs/db_01jrc22s_MYDB_1 tag = TAG20080924T025835 comment = NONE
  channel c1: complete set of backups, time: 00:07:18
  channel c1: from full datafile backupset
  
  channel c1: specifying datafile (s) in backupset including present
  current file of control in backupset including SPFILE in backupset
  channel c1: starting piece 1 to 24 - SEP-08
  channel c1: finished piece 1 to 24 - SEP-08
  
  piece handle=/oracle/10.2.0/dbs/db_02jrc2gi_MYDB_2 tag = TAG20080924T025835 comment = NONE
  channel c1: complete set of backups, time: 00:00:04
  
  Backup finished 24-SEP-08
  
  From backup to 24-SEP-08
  Current archived log
  
  output channel: c1
  
  RMAN-00571:
  ===========================================================RMAN-00569: ===============
  ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the backup command in the 2008-09-24 03:06:12
  RMAN-06059: journal archived expected not found, lost of archived newspaper compromised recoverability
  ORA-19625: error identification of file /oradata/mydb/arch/1_67_660696799.dbf
  ORA-27037: unable to get file status
  Linux error: 2: no such file or directory
  
  -----
  I have files in my/oradata/mydb/arch:
  of 1_233_660696799.dbf
  at 1_627_660696799.dbf
  
  and I do not have the 67th file. What I am doing wrong? Thnaks in advance.

  Maybe you deleted archivelog files by manuel, but your DB always remember them.

  Try: check the archivelog files:

  RMAN > overlap archivelog all;

  After that trying to delete the file expired:

  RMAN > delete all. expired archivelog

  and then re-run the script to youe.

  Note: You must remove the files by rman command archivelog:
  If you delete the command shell-> you must use rman to overlap...

  Good luck.

• Why my alert log file is not updated

  Dear all,

  Please find below my workplace

  OS - Windows server 2012

  version - 11.2.0.1.0

  Server: production server

  I checked my alert log file, there is no entry in recent day. He finally stopped on August 31. Please find entry line last two in the alert log file

  Mon Aug 31 10:30:23 2015

  Archived journal 72088 extra for each sequence 1 79292 0x38b3fdf6 dest ID thread entry 1:

  Why it is not updated after August 31.

  Please help me on the rest of my points

  (1) is there a way to know why he is not up-to-date.

  (2) If an order wrongly manually to alert the log entry, so how can I take to update as usual.

  Please make sure that you review the correct alerts log by using the following query:

  SELECT THE VALUE

  V $ diag_info

  WHERE name = "Diag Trace"

  If this is the right place, then perhaps there is no activity that should be recorded in the log of alert since August 31.

  You can manually print something for journal alerts to check this using:

  Exec DBMS_System.ksdwrt(2, 'TEST');

  Alternatively, you can manually run the command of journal and see if new lines are written to the log of alerts using the following command:

  alter system switch logfile;

• impossible to the arhcive by rman backup log.

  Hello
  
  Oracle Version: 10.2.0.2
  Operating system: linux
  
  I was unable to save the logs to archive by rman. Here, I changed the archive log destinatin also but still I get the error
  

  RMAN> backup database plus archivelog;
  
  
  Starting backup at 04-DEC-09
  current log archived
  using channel ORA_DISK_1
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03002: failure of backup plus archivelog command at 12/04/2009 16:23:18
  RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
  ORA-19625: error identifying file /u01/app/oracle/flash_recovery_area/VSMIG/archivelog/2009_09_10/o1_mf_1_3_5bkc1o5q_.arc
  ORA-27037: unable to obtain file status
  Linux Error: 2: No such file or directory
  Additional information: 3

  Published by: SIDDABATHUNI on December 4, 2009 02:59

  RMAN > delete all. expired archivelog

• Who writes the alert log file?

  Hi guys,.
  
  I tried to answer this question...
  
  What process (process backgroud) written in newspaper alert?

  Is not "one" but all background processes can / write for her.

  The archiver written for her. LogWriter can write (if you have log_checkpoints_to_alert).
  When a background process detects that another died, the former written to the alert log in before you panic the instance and kill him.

  An ALTER SYSTEM command issued by the server process for your database session will also write to the alert.log

  (Alternatively, you can call a specific procedure of data to write in it - but it is not documented).

  Hemant K Collette

• Deleted alerts log file

  What happens if alert log file is deleted?

  What happens if alert log file is deleted?

  It will be recreated again. See below

  sys@11GDEMO > show parameter background

  VALUE OF TYPE NAME
  ------------------------------------ ----------- ------------------------------
  background_core_dump partial string
  / oracle/11 g/diag/rdbms/11gdemo string background_dump_dest
  + / 11gdemo / trace +.
  sys@11GDEMO >! ls - ltr/oracle 11 g/diag/rdbms/11gdemo/11gdemo/trace/al *.
  -rw - r - 1 oracle oinstall 199294 16 Jul 03:11 /oracle/11g/diag/rdbms/11gdemo/11gdemo/trace/alert_11gdemo.log

  sys@11GDEMO >! RM /oracle/11g/diag/rdbms/11gdemo/11gdemo/trace/alert_11gdemo.log

  sys@11GDEMO >! ls /oracle/11g/diag/rdbms/11gdemo/11gdemo/trace/alert_11gdemo.log
  + ls: /oracle/11g/diag/rdbms/11gdemo/11gdemo/trace/alert_11gdemo.log: no such file or directory.

  sys@11GDEMO > alter system switch logfile;

  Modified system.

  sys@11GDEMO >! ls /oracle/11g/diag/rdbms/11gdemo/11gdemo/trace/alert_11gdemo.log
  */Oracle/11g/diag/RDBMS/11gdemo/11gdemo/trace/alert_11gdemo.log*

  sys@11GDEMO >

• Oracle errors in the alert.log

  Hello guys,.
  
  I have the setup of the Oracle Release 10.2.0.1.0 Server follows:
  -Windows 2003 Server SP2
  -3.25 GB of RAM (I think it's a 4 GB but it's a windows 2003 standard edition)
  -2 Intel Xeon Quad core
  -3 disk partitions (C - > 40 GB, 25 GB free / E-> 100 GB 85 GB free / F 300 GB-> 270 GB free)
  
  The PRISM instance configuration is:
  ARCHIVELOG: TRUE
  SGA size: 584 MB
  Full PGA size: 40 MB
  Services running (OracleDBConsolePRISM, OracleOraDb10g_home1TNSListener, OracleServeicePRISM)
  
  
  The problem is that there are only 5 users who use this database, but there are a lot of errors in the alert.log that makes the database is unavailable, the error messages are like this:

  Mon Feb 16 16:31:24 2009
  Errors in file e:\oracle\product\10.2.0\admin\prism\bdump\prism_j001_11416.trc:
  ORA-12012: error on auto execute of job 42567
  ORA-00376: file ORA-00376: file 3 cannot be read at this time
  ORA-01110: data file 3: 'E:\ORACLE\PRODUCT\10.2.0\ORADATA\PRISM\SYSAUX01.DBF'
  ORA-06512: at "EXFSYS.DBMS_RLMGR_DR", line 15
  ORA-06512: at line 1
   cannot be read at this time

  The content of prism_j001_11416.trc is:

  Dump file e:\oracle\product\10.2.0\admin\prism\bdump\prism_mmon_4620.trc
  Mon Feb 16 11:07:33 2009
  ORACLE V10.2.0.1.0 - Production vsnsta=0
  vsnsql=14 vsnxtr=3
  Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
  With the Partitioning, OLAP and Data Mining options
  Windows Server 2003 Version V5.2 Service Pack 2
  CPU                 : 8 - type 586, 2 Physical Cores
  Process Affinity    : 0x00000000
  Memory (Avail/Total): Ph:1981M/3325M, Ph+PgF:3612M/5221M, VA:1278M/2047M
  Instance name: prism
  
  Redo thread mounted by this instance: 1
  
  Oracle process number: 11
  
  Windows thread id: 4620, image: ORACLE.EXE (MMON)
  
  
  *** SERVICE NAME:(SYS$BACKGROUND) 2009-02-16 11:07:33.480
  *** SESSION ID:(161.1) 2009-02-16 11:07:33.480
  KEWRCTLRD: OCIStmtFetch Error. ctl_dbid= 1515633963, sga_dbid= 1515633963
  KEWRCTLRD: Retcode: -1, Error Message: ORA-00376: file 3 cannot be read at this time
  ORA-01110: data file 3: 'E:\ORACLE\PRODUCT\10.2.0\ORADATA\PRISM\SYSAUX01.DBF'
    *** SQLSTR: total-len=328, dump-len=240, 
        STR={select snap_interval, retention,most_recent_snap_time, most_recent_snap_id, status_flag, most_recent_purge_time, most_recent_split_id, most_recent_split_time, mrct_snap_time_num, mrct_purge_time_num, snapint_num, retention_num, swrf_version}
  *** kewrwdbi_1: Error=13509 encountered during run_once
  keaInitAdvCache: failed, err=604 
  02/16/09 11:07:33 >ERROR: exception at dbms_ha_alerts_prvt.post_instance_up308: SQLCODE -13917,ORA-13917: Posting system
   alert with reason_id 135 failed with code [5] [post_error]
  02/16/09 11:07:33 >ERROR: exception at dbms_ha_alerts_prvt.check_ha_resources637: SQLCODE -13917,ORA-13917: Posting syst
  em alert with reason_id 136 failed with code [5] [post_error]
  02/16/09 11:07:33 >parameter dump for dbms_ha_alerts_prvt.check_ha_resources
  02/16/09 11:07:33 > - local_db_unique_name (PRISM)
  02/16/09 11:07:33 > - local_db_domain (==N/A==)
  02/16/09 11:07:33 > - rows deleted (0)
  02/16/09 11:07:33 >ERROR: exception at dbms_ha_alerts_prvt.check_ha_resources637: SQLCODE -13917,ORA-13917: Posting syst
  em alert with reason_id 136 failed with code [5] [post_error]
  02/16/09 11:07:33 >parameter dump for dbms_ha_alerts_prvt.check_ha_resources
  02/16/09 11:07:33 > - local_db_unique_name (PRISM)
  02/16/09 11:07:33 > - local_db_domain (==N/A==)
  02/16/09 11:07:33 > - rows deleted (0)
  *** 2009-02-16 11:07:41.293
  ****KELR Apply Log Failed, return code 376
  *** 2009-02-16 11:08:35.294
  ****KELR Apply Log Failed, return code 376
  *** 2009-02-16 11:09:38.294
  ****KELR Apply Log Failed, return code 376
  *** 2009-02-16 11:10:41.295
  ****KELR Apply Log Failed, return code 376
  *** 2009-02-16 11:11:44.296
  ****KELR Apply Log Failed, return code 376
  *** 2009-02-16 11:12:29.328

  And this is an excerpt from the listener.log file:

  TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Production on 16-FEB-2009 11:05:44
  
  Copyright (c) 1991, 2005, Oracle.  All rights reserved.
  
  System parameter file is e:\oracle\product\10.2.0\db_1\network\admin\listener.ora
  Log messages written to e:\oracle\product\10.2.0\db_1\network\log\listener.log
  Trace information written to e:\oracle\product\10.2.0\db_1\network\trace\listener.trc
  Trace level is currently 0
  
  Started with pid=9212
  Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=akscl-mfs15.am.enterdir.com)(PORT=1521)))
  Listener completed notification to CRS on start
  
  TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
  16-FEB-2009 11:07:25 * service_register * prism * 0
  16-FEB-2009 11:07:31 * service_update * prism * 0
  16-FEB-2009 11:07:34 * service_update * prism * 0
  16-FEB-2009 11:07:37 * service_update * prism * 0
  16-FEB-2009 11:07:57 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=PRISM)(CID=(PROGRAM=\\akscl-mfs15\PRISMPM\PRISMPM.EXE)(HOST=xx-W20972)(USER=CSC3157))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.225.7)(PORT=1607)) * establish * PRISM * 0
  16-FEB-2009 11:07:58 * service_update * prism * 0
  16-FEB-2009 11:07:58 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=PRISM)(CID=(PROGRAM=\\akscl-mfs15\PRISMPM\PRISMPM.EXE)(HOST=xx-W20972)(USER=CSC3157))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.225.7)(PORT=1608)) * establish * PRISM * 0
  16-FEB-2009 11:07:58 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=PRISM)(CID=(PROGRAM=\\akscl-mfs15\PRISMPM\PRISMPM.EXE)(HOST=xx-W20972)(USER=CSC3157))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.225.7)(PORT=1612)) * establish * PRISM * 0
  16-FEB-2009 11:07:59 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=PRISM)(CID=(PROGRAM=\\akscl-mfs15\PRISMPM\PRISMPM.EXE)(HOST=xx-W20972)(USER=CSC3157))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.225.7)(PORT=1613)) * establish * PRISM * 0
  16-FEB-2009 11:07:59 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=PRISM)(CID=(PROGRAM=\\akscl-mfs15\PRISMPM\PRISMPM.EXE)(HOST=xx-W20972)(USER=CSC3157))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.225.7)(PORT=1614)) * establish * PRISM * 0
  16-FEB-2009 11:08:01 * service_update * prism * 0
  16-FEB-2009 15:05:26 * (CONNECT_DATA=(SERVICE_NAME=PRISM)(CID=(PROGRAM=C:\Program Files\Microsoft Office\OFFICE11\EXCEL.EXE)(HOST=xx-W21498)(USER=csc2682))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.131)(PORT=1999)) * establish * PRISM * 0
  16-FEB-2009 15:05:27 * (CONNECT_DATA=(SERVICE_NAME=PRISM)(CID=(PROGRAM=C:\Program Files\Microsoft Office\OFFICE11\EXCEL.EXE)(HOST=xx-W21498)(USER=csc2682))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.131)(PORT=2000)) * establish * PRISM * 0
  16-FEB-2009 17:33:26 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2513)) * establish * PRISM * 0
  16-FEB-2009 17:33:26 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2514)) * establish * PRISM * 0
  16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2515)) * establish * PRISM * 0
  16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2516)) * establish * PRISM * 0
  16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2517)) * establish * PRISM * 0
  16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2518)) * establish * PRISM * 0
  16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2519)) * establish * PRISM * 0
  16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2520)) * establish * PRISM * 0
  16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2521)) * establish * PRISM * 0
  16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2523)) * establish * PRISM * 0
  16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2524)) * establish * PRISM * 0
  16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2525)) * establish * PRISM * 0
  16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2526)) * establish * PRISM * 0
  16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2527)) * establish * PRISM * 0
  16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2528)) * establish * PRISM * 0
  16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2529)) * establish * PRISM * 0
  16-FEB-2009 17:33:27 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=PRISM)) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.180.227.18)(PORT=2530)) * establish * PRISM * 0
  16-FEB-2009 17:33:29 * service_update * prism * 0

  Please need help to solve this problem, cordially.

  Cristian Orellana says:
  Hello

  Thank you for the time, I already read something about recovery logs, but everything indicates that the redo log should be smaller and more groups, it's a small database like already post, only 5 users working in there.
  Do you think I need to increase the size of the redo log members?

  Kind regards.

  Without no doubt... but I would certainly add two members of each group and spread members around you to the disks. In its current form, with only one member of each group, if you lose a redo log, you have no redo data recovery. Problems of performance aside, your database is at risk.

• Creating the external Table to alert log

  Hello
  
  I create an external table in oracle database 11g for the alert log file monitoring (to find the ORA errors), I used this statement to create an external table
  
  Create the directory TESTForAlertLog as 'E:\oracle\product\10.2.0\admin\db\bdump '.
  
  create table Alert_Log)
  Message varchar2 (30),
  Date of the day
  )
  (external) Organization
  type oracle_loader
  Default directory TESTForAlertLog
  (settings) access
  records delimited by newline
  fields ended by ',' possibly framed by "" "
  missing field values are null
  (
  "Message."
  'DAY' DATE 'DD MM YYYY ".
  )
  )
  location ("alert_db.log")
  )
  reject limit unlimited;
  
  Output is
  
  DAY OF MSG
  
  ORACLE V10.2.0.1.0 - Production vsnsta = 0
  ORACLE V10.2.0.1.0 - Production vsnsta = 0
  ORA-1109 marked during: ALTER DATABASE CLOSE NORMAL...
  ORA-00313: open failed for the members of the group log 1 of thread 1
  ORA-00312: thread 1 1 online journal: ' E:\ORACLE\PRODUCT\10.2.0\ORADATA\db\REDO01. JOURNAL"
  ORA-27041: could not open the file
  ORA-00313: open failed for the members of the Group of newspapers wire 2 1
  ORA-00312: wire 2 1 online journal: ' E:\ORACLE\PRODUCT\10.2.0\ORADATA\db\REDO02. JOURNAL"
  ORA-27041: could not open the file
  ORA-00313: open failed for the members of Group 3, Journal of thread 1
  ORA-00312: wire 3 1 online journal: ' E:\ORACLE\PRODUCT\10.2.0\ORADATA\db\REDO03. JOURNAL"
  ORA-27041: could not open the file
  ORACLE V10.2.0.1.0 - Production vsnsta = 0
  ORACLE V10.2.0.1.0 - Production vsnsta = 0
  
  But I need the eyes of output like this
  
  
  DAY OF MSG
  
  ORACLE V10.2.0.1.0 - Production vsnsta = 0 lun 22 dec 13:10:48 2008
  ORACLE V10.2.0.1.0 - Production vsnsta = 0 lun 22 dec 13:10:48 2008
  ORA-1109 marked during: ALTER DATABASE CLOSE NORMAL...
  ORA-00313: open failed for the members of the group log 1 of thread 1
  ORA-00312: thread 1 1 online journal: ' E:\ORACLE\PRODUCT\10.2.0\ORADATA\db\REDO01. JOURNAL"Mon dec 22 13:10:48 2008
  ORA-27041: could not open the file
  ORA-00313: open failed for the members of the Group of newspapers wire 2 1
  ORA-00312: wire 2 1 online journal: ' E:\ORACLE\PRODUCT\10.2.0\ORADATA\db\REDO02. JOURNAL"Mon dec 22 13:10:48 2008
  ORA-27041: could not open the file
  ORA-00313: open failed for the members of Group 3, Journal of thread 1
  ORA-00312: wire 3 1 online journal: ' E:\ORACLE\PRODUCT\10.2.0\ORADATA\db\REDO03. JOURNAL"Mon dec 22 13:10:48 2008
  ORA-27041: could not open the file
  ORACLE V10.2.0.1.0 - Production vsnsta = 0
  ORACLE V10.2.0.1.0 - Production vsnsta = 0
  
  I need the message and time of the message occurred
  
  No idea... is it possible to get this output...
  
  
  Thank U very much
  
  Concerning
  
  SHAN

  Read this - he explains how:
  http://www.singleQuery.com/2007/02/read-the-alert-log-with-SQL/

• stop repeating the error display in the alerts log

  Dear Sir

  I use a logon trigger to the user control that connects some dev. Tools, but this caused flooding the same type of message in the alerts log. How can I keep the same message in the flood alert log.

  Kind regards

  You have all exceptions defined for data?

  exception

  When no_data_found then

  null; -do something here

  end;

• Clusterware 12.1.0.2.0: Alerts log is empty

  Hello

  After a week of working with a group at the start of two knots and 3, I see that my alertrac1.log is empty on all nodes.

  If we opt for the ORACLE_HOME for IM.

  [grid@rac1 rac1] $ pwd

  /U01/app/12.1.0/grid/log/RAC1

  [grid@rac1 rac1] $ ls - ltr

  Total 17360

  drwxr-x-. 2 root oinstall 4096 4 Mar 13:43 ctssd

  drwxr-x-. 2 root oinstall 4096 4 Mar 13:43 crsd

  drwxr-x-. 2 grid oinstall 4096 4 Mar 13:43 evmd

  drwxr-x-. 2 grid oinstall 4096 4 Mar 13:43 cssd

  drwxr-x-. 2 grid oinstall 4096 4 Mar 13:43 mdnsd

  drwxr-x-. 2 root oinstall 4096 4 Mar 13:43 gnsd

  drwxr-x-. 2 grid oinstall 4096 4 Mar 13:43 srvm

  drwxr-x-. 2 grid oinstall 4096 4 Mar 13:43 gipcd

  drwxr-x-. 2 grid oinstall 4096 4 Mar 13:43 diskmon

  drwxr-xr-x. 2 grid oinstall 4096 4 Mar 13:43 afd

  drwxrwxr-t. 5 grid oinstall 4096 4 Mar 13:43 racg

  drwxr-x-. 2 grid oinstall 4096 4 Mar 13:43 admin.

  drwxr-x-. 2 root oinstall 4096 4 Mar 13:43 crfmond

  drwxr-x-. 2 root oinstall 4096 4 Mar 13:43 crflogd

  drwxrwxr-x. 2 grid oinstall 4096 4 Mar 13:43 xag

  drwxr-xr-x. grid 6 oinstall 4096 4 Mar 13:43 acfs

  -rw-rw-r-. 1 grid 0 4 Mar 13:43 alertrac1.log oinstall

  drwxr-x-. 2 root oinstall 4096 4 Mar 13:47 ohasd

  drwxr-x-. 2 grid oinstall 4096 15 Mar 10:14 gpnpd

  drwxrwxrwt. 2 grid oinstall 4096 Mar 15 10:23 customer

  Also other newspapers, like css, crsd is empty.

  It is a question of extrange, never seem to me.

  Le Linux the servers are installed in Spanish.

  Release of Red Hat Enterprise Linux Server 6.5 (Santiago)

  However, if I change the environment variables to English.

  Messages are coming in Spanish.

  Then, if I run any command in the NETWORK user crsctl:

  [grid@rac1 ~] check crsctl $ cluster - all

  **************************************************************

  RAC1:

  CRS-4537: Cluster Ready Services Esta¡fr Lanea

  CRS-4529: Cluster Synchronization Services Esta¡fr Lanea

  CRS-4533: El gestor eventos Esta¡fr Lanea

  **************************************************************

  Rac2:

  CRS-4537: Cluster Ready Services Esta¡fr Lanea

  CRS-4529: Cluster Synchronization Services Esta¡fr Lanea

  CRS-4533: El gestor eventos Esta¡fr Lanea

  **************************************************************

  RAC3:

  CRS-4537: Cluster Ready Services Esta¡fr Lanea

  CRS-4529: Cluster Synchronization Services Esta¡fr Lanea

  CRS-4533: El gestor eventos Esta¡fr Lanea

  **************************************************************

  The messages are in Spanish, it seems me this reading env variables.

  The .bash_profile for NETWORK user is:

  export TMP = / tmp

  export TMPDIR = $TMP

  export ORACLE_HOSTNAME = rac1.localdomain

  export ORACLE_BASE = / u01/app/grid

  export ORACLE_HOME=/u01/app/12.1.0/grid

  export ORACLE_SID = + ASM1; export ORACLE_SID

  Export ORACLE_TERM = xterm; export ORACLE_TERM

  Export BASE_PATH = / usr/sbin: $PATH; export BASE_PATH

  export PATH = $ORACLE_HOME/bin: $PATH; export PATH

  export LD_LIBRARY_PATH = $ORACLE_HOME/lib: / lib: / usr/lib. export LD_LIBRARY_PATH

  Export CLASSPATH = $ORACLE_HOME/JRE: $ORACLE_HOME/jlib: $ORACLE_HOME/rdbms/jlib. Export CLASSPATH

  ulimit-u 16384-n 65536

  Export NLS_LANG = AMERICAN_AMERICA. AL32UTF8

  export LANG is en_US. UTF-

  You know only it can be past?

  
  

  Thank you very much

  Arturo

  
  

  Hello

  first I good idea to verify that the structure of diagnostic under $ORACLE_BASE and the DIAGNOSTIC_DEST

  So please follow the documentation

  http://docs.Oracle.com/database/121/Admin/diag.htm#ADMIN11008

  Secondly, what happens if you start the adrci?

  Could you open the alert.log via adrci?

  Kind regards

• How to create an incident rule to control of the 12 c Cloud Control alerts log errors

  I have a feeling it will be blinding in retrospect. I have 12 c Cloud control effective against a dozen guests and many DBs I have a rule defined for a database Instance that contains many points of interest - such as FRA filling. I chose each alert metric to see with the alerts log, including 'Generic Alert Log Error'. But I get error messages that appear in the alert log, as ORA-10173.

  Also, is there somewhere in the doco, or a data dictionary view, I can list all the parameters available?

  Thanks, helped these docs. It seems that Oracle has replaced generic monitoring with specific elements of monitoring, but it lacks some interested. However, the doc shows how this can be turned on again. Shame that it's hidden.

• ORA-12545 alert.log anti spam

  Hello

  Windows 2008 server x 64

  Oracle 11.2.0.3 x 64

  Client reported the response time very slow with the database; especially with the initial connection to the database. STATSPACK reports do not seem to show anything unusual. What is good, and it may or may have an effect on the performance of the connection, is an abundant amount of ORA-12545 error in the alert.log from the database server, so much so that since May 1st the alert.log won 300 MB in size for this single error! Precise moments show messages in the listener.log but this newspaper does not provide any error and said just that the connection has a flag "establish".

  Couple questions

  1. Within the messages it says "Tracing not lit not." - which trace must be activated and how I can further debug?
  2. When the search for the error number, it seems that this message should be on the client side and not in the alert.log to database. This makes me believe that perhaps the database trying to make connections to some other db or similar and generates this error because the tnsnames.ora servers cannot be configured for such connection. My premise is false?

  Here is the full error:

  ***********************************************************************

  Fatal OR connect error 12545, connect to:

  (LOCAL = NO.)

  VERSION INFORMATION:

  AMT for 64-bit Windows: Version 11.2.0.3.0 - Production

  Oracle leaves NT Protocol adapter for 64-bit Windows: Version 11.2.0.3.0 - Production

  Adapter protocol NT Windows NT TCP/IP for Windows 64-bit: 11.2.0.3.0 - Production Version

  Time: May 23, 2014 10:37:57

  Tracing not lit.

  AMT error struct:

  NS main err in code: 12545

  TNS-12545: Connect failed because target host or object does not exist

  NS secondary err code: 12560

  NT main err in code: 0

  NT secondary err code: 0

  NT OS err code: 0

  abandonment of opiodr treat unknown ospid (7604) following ORA - 609

  Thank you

  -joel

  In general, you now know which pollute the file alert_SID.log

  This is the code that runs on the Server DB that tries to access a remote database & fails.

  Oracle DB is the victim; not the culprit.