Snapshot of database

Hello,
I created a snapshot of SQL 2008 database. The goal in my case was to use it for reporting and client querying instead of using Production database.
I'm planning to drop and create it again daily.
My question and confusion is:
1.is this snapshot static or dynamic? I mean ... in case I will do some changes in 'source' database will it be reflected in snapshot immediately or only after I drop and create snapshot again?
2. could I use Toad feature for creating snapshot and using Job scheduler for daily recreate or better run script myself ( could I set schedule on script inside Toad or MS Studio?)
Thanks
EV

The goal in my case was to use it for reporting and client querying instead of using Production database.
Hello,
Please note: A snapshot is not a stand-alone copy, all unchanged data will be read from the source data, so there won't be any performance benefit with this solution, you only freeze the data to the time where you created the snapshot.
Olaf Helper
[ Blog] [ Xing] [ MVP]
Not sure what you meant by 'all unchanged data ..'
Since snapshot is 'static' why we are talking about any 'changed' data?
In any case the goal in my case is to avoid using Production server because it tends to lock tables when running long queries. We also have a 'copy' of production server that is made every 15 minutes but it fail to 'copy' when Production is in use by someone
Anyway ... the goal is to avoid using Production server ... and diff in one day between Snapshot and Production for reports and client querying is acceptable for us.
Still didn't get if Production server will be impacted when someone uses Snapshot? Are you statiting that Production server will be used when someone use Snapshot? If it's 'true' ...likely I'll have to reconsider this approach and maybe better use
'copy' of my Production since using 'copy' will not impact on Production ...Could you please clarify on that?
Thanks
EV

Similar Messages

Snapshot standby database in oracle 11g r2 RAC

Folks,
i am just wondering if the process is same for standalone and RAC snapshot standby database.
We have a DR test
1 / I just converted the standalone DR on 11g to snapshot standby database for users to do some testing and reverted back to physical standby after test was done. i folllowed metalink note ID 443720.1
2/ now there is anotherDR test where we have 2 node prod and 2 node DR on oracle 11g rel2 RAC, so not sure we can follow the same process that i used for 11g standalone database. If somebody have done this on RAC, would you please provide the steps ?
Thanks in advance
SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
TNS for Linux: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
SQL> !uname -a
Linux 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux

I haven't done a Snapshot Standby (RAC or non-RAC). But I see no reason why it shouldn't work with a RAC Standby either.
The command is a Database level command, not an Instance level command.
Hemant K Chitale

Error in viewing snapshots Oracle database 10g

Database 10g rl 2 (RAC)
Os hp-ux 11i
I am trying to collect snapshot of database using ADDM, getting following error.
The details for this snapshot cannot be displayed. Either the snapshot is purged/deleted, or it is the first snapshot after an instance shutdown

Hi,
I checked the snapshot id and now when i am taking the snapshot it is giving the following error:
SQL Error
ORA-13509: error encountered during updates to a AWR table ORA-01691: unable to extend lob segment ORA-01691: unable to extend lob segment SYS.SYS_LOB0000008938C00038$$ by 128 in tablespace SYSAUX . by in tablespace ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 10 ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 33 ORA-06512: at line 1

Problem Converting standby database from snapshot to physical

Any help willl be greatly appreciated...
I am trying to convert a standby database that is in "snapshot" mode back to "physical" standby and I am encountering problems in the process from the "DGMGRL" command line.
Both instances are on the same physical machine. Everything was working fine untill I tried to change the db from snapshot to physical. The DGMGRL starts the conversion process and is able to shutdown but when trying to restart the instance is fails and reports that the service is not defined.
Here is the issue I am facing:
C:\app\MMJ\product\11.1.0\db_1\BIN>
C:\app\MMJ\product\11.1.0\db_1\BIN>set ORACLE_SID=I11G1 <======= the primary database
C:\app\MMJ\product\11.1.0\db_1\BIN>dgmgrl
DGMGRL for 32-bit Windows: Version 11.1.0.6.0 - Production
Copyright (c) 2000, 2005, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/password@i11g1sb <===== the standby database currently in snapshot mode
Connected.
DGMGRL> connect sys/password@i11g1 <==== the primary database
Connected.
DGMGRL> convert database 'i11g1sb' to physical standby;
Converting database "i11g1sb" to a Physical Standby database, please wait...
Operation requires shutdown of instance "i11g1sb" on database "i11g1sb"
Shutting down instance "i11g1sb"...
Database closed.
Database dismounted.
ORACLE instance shut down.
Operation requires startup of instance "i11g1sb" on database "i11g1sb"
Starting instance "i11g1sb"...
Unable to connect to database
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Failed.
You are no longer connected to ORACLE
Please connect again.
Unable to start instance "i11g1sb"
You must start instance "i11g1sb" manually
Failed to convert database "i11g1sb"
DGMGRL> show configuration
Configuration
Name: DGConfig1
Enabled: YES
Protection Mode: MaxPerformance
Databases:
i11g1 - Primary database
i11g1sb - Snapshot standby database (disabled)
Fast-Start Failover: DISABLED
Current status for "DGConfig1":
SUCCESS
DGMGRL> exit
C:\app\MMJ\product\11.1.0\db_1\BIN>set ORACLE_SID=I11G1SB
C:\app\MMJ\product\11.1.0\db_1\BIN>sqlplus /nolog
SQL*Plus: Release 11.1.0.6.0 - Production on Wed Mar 25 11:40:16 2009
Copyright (c) 1982, 2007, Oracle. All rights reserved.
SQL> connect / as sysdba
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 426852352 bytes
Fixed Size 1333648 bytes
Variable Size 369100400 bytes
Database Buffers 50331648 bytes
Redo Buffers 6086656 bytes
Database mounted.
Database opened.
==============>>>> as you can see I can start the standby database without any problems and even query the table in which I made some changes. I had added the record with "Region_ID"=30. I have
SQL> select * from hr.regions;
REGION_ID REGION_NAME
30 JAPAC
1 Europe
2 Americas
3 Asia
4 Middle East and Africa
SQL>
The same table on the primary database has the following records in the same table:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\MMJ>set ORACLE_HOME=c:\app\mmj\product\11.1.0\db_1
C:\Documents and Settings\MMJ>set ORACLE_SID=i11g1
C:\Documents and Settings\MMJ>
C:\Documents and Settings\MMJ>cd %ORACLE_HOME%
C:\app\MMJ\product\11.1.0\db_1>cd bin
C:\app\MMJ\product\11.1.0\db_1\BIN>
C:\app\MMJ\product\11.1.0\db_1\BIN>
C:\app\MMJ\product\11.1.0\db_1\BIN>sqlplus /nolog
SQL*Plus: Release 11.1.0.6.0 - Production on Wed Mar 25 11:43:10 2009
Copyright (c) 1982, 2007, Oracle. All rights reserved.
SQL> connect / as sysdba
Connected.
SQL>
SQL> select * from hr.regions;
REGION_ID REGION_NAME
1 Europe
2 Americas
3 Asia
4 Middle East and Africa
20 JAPAC
40 JAPAC
6 rows selected.
SQL>
=======> The TNSPING works fine against both the databases.
C:\app\MMJ\product\11.1.0\db_1\BIN>set O
ORACLE_HOME=c:\app\mmj\product\11.1.0\db_1
ORACLE_SID=I11G1SB
OS=Windows_NT
C:\app\MMJ\product\11.1.0\db_1\BIN>
C:\app\MMJ\product\11.1.0\db_1\BIN>tnsping i11g1sb
TNS Ping Utility for 32-bit Windows: Version 11.1.0.6.0 - Production on 25-MAR-2009 16:56:42
Copyright (c) 1997, 2007, Oracle. All rights reserved.
Used parameter files:
c:\app\mmj\product\11.1.0\db_1\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = MHost)(PORT = 1523))) (CONNECT_DATA = (SERVICE_NAM
E = I11G1SB)))
OK (230 msec)
C:\app\MMJ\product\11.1.0\db_1\BIN>tnsping i11g1
TNS Ping Utility for 32-bit Windows: Version 11.1.0.6.0 - Production on 25-MAR-2009 16:56:47
Copyright (c) 1997, 2007, Oracle. All rights reserved.
Used parameter files:
c:\app\mmj\product\11.1.0\db_1\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = MHost)(PORT = 1523))) (CONNECT_DATA = (SERVICE_NAM
E = I11G1)))
OK (30 msec)
C:\app\MMJ\product\11.1.0\db_1\BIN>lsnrctl
LSNRCTL for 32-bit Windows: Version 11.1.0.6.0 - Production on 25-MAR-2009 16:57:01
Copyright (c) 1991, 2007, Oracle. All rights reserved.
Welcome to LSNRCTL, type "help" for information.
LSNRCTL> set current_listener i11g1
Current Listener is i11g1
LSNRCTL> services
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=MHost)(PORT=1523)))
Services Summary...
Service "I11G1" has 1 instance(s).
Instance "I11G1", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:1 refused:0
LOCAL SERVER
Service "I11G1SB" has 1 instance(s).
Instance "I11G1SB", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:55 refused:1
LOCAL SERVER
Service "I11G1SB_DGMGRL" has 1 instance(s).
Instance "I11G1SB", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Service "i11g1.mhost" has 1 instance(s).
Instance "i11g1", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:6 refused:0 state:ready
LOCAL SERVER
Service "i11g1XDB.mhost" has 1 instance(s).
Instance "i11g1", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1022 state:ready
DISPATCHER <machine: MHost, pid: 3944>
(ADDRESS=(PROTOCOL=tcp)(HOST=MHost)(PORT=1430))
Service "i11g1_DGB.mhost" has 1 instance(s).
Instance "i11g1", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:6 refused:0 state:ready
LOCAL SERVER
Service "i11g1_XPT.mhost" has 1 instance(s).
Instance "i11g1", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:6 refused:0 state:ready
LOCAL SERVER
Service "i11g1sb.mhost" has 1 instance(s).
Instance "i11g1sb", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
LOCAL SERVER
Service "i11g1sbXDB.mhost" has 1 instance(s).
Instance "i11g1sb", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1022 state:ready
DISPATCHER <machine: MHost, pid: 7336>
(ADDRESS=(PROTOCOL=tcp)(HOST=MHost)(PORT=1931))
Service "i11g1sb_DGB.MHost" has 1 instance(s).
Instance "i11g1sb", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
LOCAL SERVER
Service "i11g1sb_XPT.mhost" has 1 instance(s).
Instance "i11g1sb", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
LOCAL SERVER
The command completed successfully
LSNRCTL>

Thanks for the response.
So, here is the status now....with a little background...
After my original post, I started to read the manuals and I found the sql command to convert the database back from snapshot to physical standby (sb).
That worked fine and I had my snapshot sb back to physical sb.
So when you posted the suggestion, I already had my db in physical sb mode. I said no problem, I will convert it back to snapshot and then back again using dgmgrl instead of sql+
Well here is how my listener is configured now.
SID_LIST_I11G1 =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = I11G1.MHOST)
(ORACLE_HOME = c:\app\mmj\product\11.1.0\db_1)
(SID_NAME = I11G1)
(SID_DESC =
(GLOBAL_DBNAME = I11G1SB.MHOST)
(ORACLE_HOME = c:\app\mmj\product\11.1.0\db_1)
(SID_NAME = I11G1SB)
(SID_DESC =
(GLOBAL_DBNAME = I11G1SB_DGMGRL)
(ORACLE_HOME = c:\app\mmj\product\11.1.0\db_1)
(SID_NAME = I11G1SB)
Then using dgmgrl I tried to change the db from p-sb to s-sb and the results are not good....
"i11g1 >"dgmgrl
DGMGRL for 32-bit Windows: Version 11.1.0.6.0 - Production
Copyright (c) 2000, 2005, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL>
DGMGRL> connect sys/[email protected]
Connected.
DGMGRL>
DGMGRL>
DGMGRL> convert database 'i11g1sb' to snapshot standby;
Converting database "i11g1sb" to a Snapshot Standby database, please wait...
Database "i11g1sb" converted successfully
DGMGRL> show configuration
Configuration
Name: DGConfig1
Enabled: YES
Protection Mode: MaxPerformance
Databases:
i11g1 - Primary database
i11g1sb - Snapshot standby database
Fast-Start Failover: DISABLED
Current status for "DGConfig1":
Warning: ORA-16607: one or more databases have failed
DGMGRL> show configuration
Configuration
Name: DGConfig1
Enabled: YES
Protection Mode: MaxPerformance
Databases:
i11g1 - Primary database
i11g1sb - Snapshot standby database
Fast-Start Failover: DISABLED
Current status for "DGConfig1":
Warning: ORA-16607: one or more databases have failed
DGMGRL> show database 'i11g1sb';
Database
Name: i11g1sb
Role: SNAPSHOT STANDBY
Enabled: YES
Intended State: APPLY-OFF
Instance(s):
i11g1sb
Current status for "i11g1sb":
SUCCESS
DGMGRL> show database 'i11g1';
Database
Name: i11g1
Role: PRIMARY
Enabled: YES
Intended State: TRANSPORT-ON
Instance(s):
i11g1
Current status for "i11g1":
Error: ORA-16778: redo transport error for one or more databases
DGMGRL> exit
Not sure if the following (notice the typo in the service name) in the parameter (log_archive_dest_2) definition on the standby d/b has anything to do with this. I did not get this error when I initially converted to s-sb.
also I checked all my session notes, I did not type the command to set this parameter on the standby d/b and so it was not a typo on my part. However, it seems to have come from the rman script supplied with the obe. This script is supposed to clone the primary d/b to a standby db and in the process replace the string /i11g1/ with /i11g1sb/.
SQL> show parameter log_archive_dest_2
NAME TYPE VALUE
log_archive_dest_2 string service=i11g1sbsb async valid_
for=(online_logfile,primary_ro
le) db_unique_name=i11g1sb
SQL>
SQL>
SQL> select instance_name from v$instance;
INSTANCE_NAME
i11g1sb
SQL>
Given all this, the archive logs seem to be shipping correctly to the sby d/b.
"i11g1sb >"cd C:\app\MMJ\flash_recovery_area\i11g1sb\ARCHIVELOG\2009_03_30
"i11g1sb >"dir
Volume in drive C is Local Disk
Volume Serial Number is 3189-6472
Directory of C:\app\MMJ\flash_recovery_area\i11g1sb\ARCHIVELOG\2009_03_30
30/03/2009 09:05 PM <DIR> .
30/03/2009 09:05 PM <DIR> ..
30/03/2009 05:41 PM 35,627,008 O1_MF_1_137_4X2H4JJM_.ARC
30/03/2009 05:41 PM 1,910,784 O1_MF_1_138_4X2H4LVC_.ARC
30/03/2009 09:04 PM 10,447,360 O1_MF_1_139_4X2V03RW_.ARC
30/03/2009 09:05 PM 8,654,848 O1_MF_1_140_4X2V3BWB_.ARC
4 File(s) 56,640,000 bytes
2 Dir(s) 39,716,225,024 bytes free
"i11g1sb >"
"i11g1 >"dir
Volume in drive C is Local Disk
Volume Serial Number is 3189-6472
Directory of C:\app\MMJ\flash_recovery_area\I11G1\ARCHIVELOG\2009_03_30
30/03/2009 09:05 PM <DIR> .
30/03/2009 09:05 PM <DIR> ..
30/03/2009 04:09 PM 35,627,008 O1_MF_1_137_4X29QHTV_.ARC
30/03/2009 04:24 PM 1,910,784 O1_MF_1_138_4X2BMOC7_.ARC
30/03/2009 06:32 PM 10,447,360 O1_MF_1_139_4X2L4J3X_.ARC
30/03/2009 09:05 PM 8,654,848 O1_MF_1_140_4X2V37KL_.ARC
4 File(s) 56,640,000 bytes
2 Dir(s) 39,716,229,120 bytes free
I am tempted to start all over again, but I'd rather use this opportunity to debug this issue (as a learning exercise). I can always start from scratch. That brings up another Q: What do I need to do to blow away all traces of the stand by database (including all the archive logs etc...) keeping my primary intact. I'd also like to blow away all snapshot and archive logs for the primary as well.

Cannot Convert standby database from snapshot to physical

Hello all,
I am using Oracle Entreprise version 11gR1 and had made the followings configuration:
- ANAISMD2 : primary database+_+
- ANAISMD3 : physical standby datbase. Created via RMAN
Both are located on the same host running a RH 4.
ANAISMD3 is maintained successfully with the primary.
I can make a fail-over between the both: it works fine.
I can convert ANAISMD3 from physical to snapshot via DGMGRL: it works fine
But I cannot convert back ANAISMD3 to physical, got an error ORA-12514
I had checked also the listener service for both ANAISMD2/ANAISMD3 before launching the conversion:
- the services shown on ANAISMD3 seems correct e.g. ANAISMD2 is seen as a remote server.
- but on ANAISMD2, ANAISMD3 seems incorrect e.g. ANAISMD3 is seen as a local server.
I had attached some screen shots of dg/lsnrctl results;
What are the mistakes
Thank in advance for support
==> Before I made the conversion , DGMGRL shows correct primary/standby status:
DGMGRL for Linux: Version 11.1.0.6.0 - Production
Copyright (c) 2000, 2005, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/oracle@ANAISMD2
Connected.
DGMGRL> show configuration
Configuration
Name: ANAIS
Enabled: YES
Protection Mode: MaxPerformance
Databases:
ANAISMD2 - Primary database
ANAISMD3 - Snapshot standby database
Fast-Start Failover: DISABLED
Current status for "ANAIS":
SUCCESS
==> When I want to convert back ANAISMD3 to physical, I got the following errors from the listener:_
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/oracle@ANAISMD2
Connected.
DGMGRL> convert database 'ANAISMD3' to physical standby;
Converting database "ANAISMD3" to a Physical Standby database, please wait...
Operation requires shutdown of instance "ANAISMD3" on database "ANAISMD3"
Shutting down instance "ANAISMD3"...
Database closed.
Database dismounted.
ORACLE instance shut down.
Operation requires startup of instance "ANAISMD3" on database "ANAISMD3"
Starting instance "ANAISMD3"...
Unable to connect to database
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Failed.
You are no longer connected to ORACLE
Please connect again.
Unable to start instance "ANAISMD3"
You must start instance "ANAISMD3" manually
Failed to convert database "ANAISMD3"
DGMGRL>
==> Here ist he listener.ora_ (I put the same for both ANAISMD2/ANAISMD3 with port 1541/1551). Note: DGB is the accepted extension for dgmgrl service (instead of DGMGRL as mentionned in documentation).
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL=TCP) (HOST=rh4-2a) (PORT=1541))
TRACE_LEVEL_LISTENER = ADMIN
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME=/home/oracle/product/11.1.0)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = ANAISMD2)
(GLOBAL_DBNAME = ANAISMD2.world)
(ORACLE_HOME=/home/oracle/product/11.1.0)
(SID_DESC =
(SID_NAME = ANAISMD2)
(GLOBAL_DBNAME = ANAISMD2_DGB.world)
(ORACLE_HOME=/home/oracle/product/11.1.0)
(SID_DESC =
(SID_NAME = ANAISMD3)
(GLOBAL_DBNAME = ANAISMD3_DGB.world)
(ORACLE_HOME=/home/oracle/product/11.1.0)
(SID_DESC =
(SID_NAME = ANAISMD3)
(GLOBAL_DBNAME = ANAISMD3.world)
(ORACLE_HOME=/home/oracle/product/11.1.0)
==> Here is the tnsnames.ora (I put the same for both ANAISMD2/ANAISMD3 with port 1541/1551).
ANAISMD2.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = rh4-2a)(PORT = 1541))
(CONNECT_DATA =
(SERVICE_NAME = ANAISMD2_DGB.world)
ANAISMD3.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = rh4-2a)(PORT = 1551))
(CONNECT_DATA =
(SERVICE_NAME = ANAISMD3_DGB.world)
==> Here is the sqlnet.ora (same on both):
TRACE_LEVEL_CLIENT = OFF
DIAG_ADR_ENABLED=FALSE
DIAG_DDE_ENABLED=FALSE
DIAG_SIGHANDLER_ENABLED=FALSE
names.directory_path = (TNSNAMES)
names.default_domain = world
name.default_zone = world
==>
==> List of services provided by the listener of ANAISMD2:
LSNRCTL for Linux: Version 11.1.0.6.0 - Production on 10-AUG-2009 16:39:36
Copyright (c) 1991, 2007, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=rh4-2a)(PORT=1541)))
Services Summary...
Service "ANAISMD2.world" has 1 instance(s).
Instance "ANAISMD2", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
+"DEDICATED" established:0 refused:0+
LOCAL SERVER
Service "ANAISMD2_DGB.world" has 1 instance(s).
Instance "ANAISMD2", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
+"DEDICATED" established:3 refused:0+
LOCAL SERVER
Service "ANAISMD3.world" has 1 instance(s).
Instance "ANAISMD3", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
+"DEDICATED" established:0 refused:0+
LOCAL SERVER
Service "ANAISMD3_DGB.world" has 1 instance(s).
Instance "ANAISMD3", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
+"DEDICATED" established:0 refused:0+
LOCAL SERVER
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
+"DEDICATED" established:0 refused:0+
LOCAL SERVER
The command completed successfully
==> List of services provided by the listener of ANAISMD3:
Services Summary...
Service "ANAISMD2.world" has 2 instance(s).
Instance "ANAISMD2", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Instance "ANAISMD2", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
REMOTE SERVER
(ADDRESS=(PROTOCOL=TCP)(HOST=rh4-2)(PORT=1521))
Service "ANAISMD2_DGB.world" has 2 instance(s).
Instance "ANAISMD2", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Instance "ANAISMD2", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
REMOTE SERVER
(ADDRESS=(PROTOCOL=TCP)(HOST=rh4-2)(PORT=1521))
Service "ANAISMD2_XPT.world" has 1 instance(s).
Instance "ANAISMD2", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
REMOTE SERVER
(ADDRESS=(PROTOCOL=TCP)(HOST=rh4-2)(PORT=1521))
Service "ANAISMD3.world" has 1 instance(s).
Instance "ANAISMD3", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Service "ANAISMD3_DGB.world" has 1 instance(s).
Instance "ANAISMD3", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
The command completed successfully

You need to have static service registered with listener in this way. This is must because as you know when it converts db that time it shutsdown dbs also so all dynamic services are lost and dgmgrl is not ale to connect to db hence conversion fails.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = ORACLE_SID)
(GLOBAL_DBNAME=db_unique_name_DGMGRL.db_domain)
(ORACLE_HOME = /apps/oracle/product/11.1.0)
Plus with this make a entry in tnsnames.ora using service name from above or check from lsnrctl status look for service "db_unique_name_DGMGRL.db_domain"
e.g. this is my best practice how i give the names to tns entry
db_unique_name_DGMGRL =
(DESCRIPTION =
(SDU = 32767)
(ADDRESS = (PROTOCOL = TCP)(HOST = hostname)(PORT = port))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = db_unique_name_DGMGRL.db_domain)
Define same way in both primary and standby db.
Now use these tns entries to create configuration.
e.g.
create configuration prim_db as primary database is db_unique_name connect identifier is "db_unique_name_DGMGRL";
-- db_unique_name_DGMGRL from primary tns entry
add database stdby_db as connect identifier is "db_unique_name_DGMGRL" MAINTAINED AS PHYSICAL;
-- db_unique_name_DGMGRL from standby db tns entry
hope this will help

How snapshot is handel at the time of database recover.

hi, (sqlserver 2008r2)
in following link
https://technet.microsoft.com/en-us/library/ms173763(v=sql.105).aspx
in SNAPSHOT para
"Except
when a database is being recovered, SNAPSHOT transactions do not request locks when reading data. SNAPSHOT transactions reading data do not block other transactions from writing data. Transactions writing data do not block SNAPSHOT transactions from reading
data."
1) please tel me how it handels snapshot transactions in database recovery ?
2) In how many cases database goes in recover and how often?
3) This is from the above link please tel me if have under stood correctlly
"When the snapshot isolation level is enabled, if you are deleting a row on a heap (a table without clustered index) and the transaction
log fills before the log record for ghost row is persisted, the database is taken offline. If this occurs, the database will automatically restart, undergo a full recovery, and come online."
my question is by saying "When the snaphot isolation level is enabled" that means when
"ALLOW_SNAPSHOT_ISOLATION " Command is used to enable snapshot in database not the setting of snapshot isolation
in any query so that one can start transaction?
yours
sincerly

Hi,
The snapshot option is similar to the serializable isolation level. Therefore the reading data is always the last committed version of the row as this isolation level uses row versioning instead of shared locks.
1) this transaction relies on row versioning and is visible after you have committed it.
2)When using the syntax " ALTER DATABASE DBNAME SET ALLOW_SNAPSHOT_ISOLATION ON;", you will enable snapshot for the entire database.
3)What I understand is that when you delete a row and this transaction is not committed it will not be visible for the reader, because reading data is only possible of the last committed version as snapshot is based on row versioning.
Hopefully this answers you question.
If this answers your question please propos it as an answer.
Reshma

Why can't the snapshot be refreshed properly?

I have created a snapshot(read_only) but it can't be refreshed with the master table properly. I found that after I created the snapshot, any change made in the master table was not reflected in the snapshot table.
Here is my SQL statement for creating the snapshot.
CREATE SNAPSHOT testing
TABLESPACE XXX
STORAGE (INITIAL 32K NEXT 32K)
REFRESH NEXT sysdate+1
WITH ROWID
AS SELECT *
from master_table@master_site_database;
The SQL statement is to create the snapshot. and refresh the snapshot with master table every day.By executing the SQL,the snapshot is created successfully,but seem not to be freshed properly. The master_site_database, which the master_table locates, is Oracle version 7. The snapshot site database ,which the snapshot is created in, is Oracle version 8.
Any suggestions will be greatly appreciated. Thanks in advance.
Helena

Please see our guidelines for accessing remote ejbs from clients in our EJB FAQ :
https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html
--ken

Refresh Collection Snapshots Error ORA-12008 ORA-01555

Need some insight!
Ct is implementing R12.1.1 ASCP using existing 11.5.10 EBS as source.
In source EBS, when running Refresh Collection Snapshots (RCS) in COMPLETE mode, we encounter this error:
ORA-12008: error in materialized view refresh path
ORA-01555: snapshot too old: rollback segment number 13 with name "_SYSSMU13$" too small
ORA-12008: error in materialized view refresh path
ORA-01555: snapshot too old: rollback segment number 13 with name "_SYSSMU13$" too small
All the snapshot entities got refreshed successfully (in 5 minutes) but the Refresh Collection Snapshot request itself ends with ERROR (after 4 hrs).
Appreciate your input on this one.
Thanks,
Jake

Welcome to the forums !
ORA-01555 is a common error condition. There are typically two solutions (or a combination of both) -
1. Increase rollback / undo tablespace size
2. Run your process when the database is not active (i.e. few or no updates/deletes/inserts etc).
More information may be available in these MOS Docs
211121.1 - How To Run MSRFWOR - Refresh Collections Snapshots Concurrent Request From The Application
207644.1 - Data Collections is Failing - All Errors - First Diagnostic Steps
306418.1 - 11.5.10 MSRFWOR: Refresh Collection Snapshot Performance Is Poor and Fails with Errors
369173.1 - MSRFWOR Refresh Collection Snapshots Performance Database Bug 4196039
308487.1 - Refresh Collection Snapshot Request Fails Yet The Request Shows Complete Normal
HTH
Srini

Duplicate database and incremental backups

Hello,
I'm currently investigating options to maintain a test server that is "relatively" up-to date compared to the production server.
This is my first contact with RMAN and I went through the manuals but as I did not have a chance to play with it I might have missed something.
This is an Oracle 11.2 (not sure about the full version number) on a Redhat Enterprise Linux.
The test server needs to be writeable and need to be re-synced with the production server approx. once or twice a month. Due to the size of the database (~600GB) we are looking into solutions that could make use of the incremental backups that are already taken on the production database.
While initiating the test server using RMAN DUPLICATE seems to be straight forward, I'm unsure on how the "syncing" can be done in the most efficient way - especially because we are changing the data on the test server.
From the description of the RMAN RECOVER command it's not clear to me if this could be used to "recover" the test database based on the incremental backups to the "current state" of the production database even if the test database has been changed. After reading some posts here, this does not seem to be the case.
Would a restore point make such an incremental restore possible? Creating a (named?) restore point right after the duplication, then once the tests are finished do a flashback to the restore point and then apply the incremental backups that have accumulated since then.
Another options seems to be to create a Standby Database. Then when performing the tests we turn the Standby Database into a Snapshot Standby Database open it in read/write and run the tests. Once we are done, we switch it back to a physical standby. That switchback will rewind the changes and the accumulated redo logs are applied thus "incrementally" catching up with production - which is essentially what we want.
Is there any other solution to this? Or is using a snapshot standby the most efficient solution? If at all possible we would like to avoid transferring the 600GB each time we want to re-sync the test database.
Thanks in advance
Thomas

Thomas;
RMAN Incremental Backups to Roll Forward a Physical Standby Database might offer some help.
There's a great example of it here :
http://www.oracle-ckpt.com/?s=standby+scn&op.x=0&op.y=0
If you go the Snapshot route make sure you have the space for the Archive on both databases. Also double check you flash recovery area, again on both databases. If you have an issue you may have to use the roll forward.
Best Regards
mseberg

Active data guard standby database

Hello,
we have to choose which technology to use for maintain Oracle backup center synchronized with main center. This backup center should be read only, and data generated in main should be replicated into backup. So I would like to use Active Data Guard, but I have a possible issue with reading in backup center, because reading is not just select, but filling(inserting data) some temporary tables (from client side, and from procedures in database). Will Standby database in backup center allow this if Active Data Guard is used. We would go with Oracle 11gR2.
Also other suggestions on replication technologies (I know there are RAC, ADG, Oracle Streams, Golden Gate), or any document which would help us decide which of these technologies would suit our needs the best.
Thank You.

Hi,
user12121832 wrote:
we have to choose which technology to use for maintain Oracle backup center synchronized with main center. This backup center should be read only, and data generated in main should be replicated into backup. So I would like to use Active Data Guard, but I have a possible issue with reading in backup center, because reading is not just select, but filling(inserting data) some temporary tables (from client side, and from procedures in database). Will Standby database in backup center allow this if Active Data Guard is used. We would go with Oracle 11gR2. You can use Standby Database to make yours Backup.
In 11.1 or later you can use feature "Snapshot Standby Databases" if this write on database is temporary (i.e you will not use the new data) and at backup time you not need use Snapshot Standby Database feature.
A snapshot standby database is a physical standby database that you temporarily convert into an updatable standby database. You can use snapshot standby databases as clones or test databases to validate new functionality and new releases, and when finished you then convert the database back into a physical standby. While running in the snapshot standby database role, it continues to receive and queue redo data so that data protection and the RPO are not sacrificed.
A snapshot standby database has the following characteristics:
* A snapshot standby database cannot be the target of a switchover or failover. A snapshot standby database must first be converted back into a physical standby database before performing a role transition to it.
* A snapshot standby database cannot be the only standby database in a Maximum Protection Data Guard configuration.
Note:
Flashback Database is used to convert a snapshot standby database back into a physical standby database. Any operation that cannot be reversed using Flashback Database technology will prevent a snapshot standby from being converted back to a physical standby.
http://docs.oracle.com/cd/E11882_01/server.112/e17157/unplanned.htm#HAOVW11832
Also other suggestions on replication technologies (I know there are RAC, ADG, Oracle Streams, Golden Gate), or any document which would help us decide which of these technologies would suit our needs the best.If you need "standby" database opened in read-write all time the best option is to use Golden Gate.
Regards,
Levi Pereira

Reg: Exporting the data from the Physical Standby database system.

Hello all,
We have an oracle standard edition one 11gR1 environment, in which i need to export the data from the physical standby system.
So can anyone suggest me, How to do it safely (mount state).
Regards,
Konda.

Hi,
You can use "exp" utility to export the database from a read only database whereas you can't export the read only database using "expdp".
Since you are using version 11g, it is not advisable to use exp. You can convert your standby to snapshot database, open read, write and export the database using expdp and then again convert it to standby.
This is a very easy process which we follow in our company to do testing when required.
Follow note 11g Using Snapshot Standby Database. (Doc ID 443720.1) for converting and usage.
Thank you!!

Snap ids to generate performance report

Hi,
I have a basic idea on statspack, and implementing this first time, looking for your help to generate statspack report.
scenario is this :-
we have to do a performance testing during bulk loading which happens daily at night for 1 hour.
i have sheduled a job to generate snaps on every interval of 15 min say :-
NAME SNAP_ID Date/Time
oracle 4 13.11.2006:08:45:00
oracle 1 13.11.2006:08:00:00
oracle 2 13.11.2006:08:15:00
oracle 3 13.11.2006:08:30:00
suppose at 08:00 there is no loading so i am considering this as a baseline snap ,
so, which snap ids i have to include to generate various performance report (like sp_1_2,sp_1_3,sp_14 etc) .
Asif

Snap is a snap. A snapshot of database status at a given point in time. Statspack was designed to help DBA's diagnose the performance problems of a database during a particular interval of time by recording what all went on with the database.
If you are trying to analyze the database using only one snap, you will never get the correct picture.
Lets say in your case, you generate the report s_1 only which is before load. How will you diagnose the problem that happened after this snap?

Background job failing - ECC 6.0, Solution Manager 7.0

Dear All,
Four days back, I have installed the Solution Manager 7.0 and ECC 6.0 on
HPUX IA64 hardware with database as Oracle 10.2.0.2.0 (Unicode).
In both server, latest kernel patch has been applied.
The Support package versions are (both server):
KERNEL (Release 700)      146
SAP_BASIS           0014
SAP_ABA           0014
PI_BASIS(2005_1_700)      0014
ST-PI                0005
SAP_BW                0016
While checking the the jobs from SM37, in both the server,
I am observing that following jobs are always failing with
same reason:
SAP_COLLECTOR_FOR_PERFMONITOR
=============================
Date       Time     Message text                                                           Message class Message no. Message type
========== ======== ====================================================================== ============= =========== ============
15.05.2008 06:25:12 Job started                                                                 00           516          S
15.05.2008 06:25:12 Step 001 started (program RSCOLL00, variant , user ID BGDUSER)              00           550          S
15.05.2008 06:25:18 Clean_Plan:Cleanup of DB13 Plannings                                       DB6PM         000          S
15.05.2008 06:25:18 Clean_Plan:started by RSDBPREV                       on server gcbeccd     DB6PM         000          S
15.05.2008 06:25:18 Clean_Plan:Cleaning up jobs of system RD3                                  DB6PM         000          S
15.05.2008 06:25:18 Clean_Plan:finished                                                        DB6PM         000          S
15.05.2008 06:25:18 Database system not supported                                               S1           101          S
15.05.2008 06:25:36 ABAP/4 processor: DBIF_DSQL2_SQL_ERROR                                      00           671          A
15.05.2008 06:25:36 Job cancelled                                                               00           518          A
SAP_REORG_UPDATERECORDS
=======================
Date       Time     Message text                                                          Message class Message no. Message type
========== ======== ===================================================================== ============= =========== ============
14.05.2008 00:31:01 Job started                                                                00           516          S
14.05.2008 00:31:01 Step 001 started (program RSM13002, variant SAP&001, user ID BGDUSER)      00           550          S
14.05.2008 00:31:01 Reorganization of update date not allowed in batch                         15           100          A
14.05.2008 00:31:02 Job cancelled                                                              00           518          A
SAP_WP_CACHE_RELOAD_FULL
========================
Date       Time     Message text                                                                                Message class Message no. Message type
========== ======== ============================================================================================ ============= =========== ============
15.05.2008 00:30:11 Job started                                                                                00           516          S
15.05.2008 00:30:11 Step 001 started (program RWP_RUNTIME_CACHE_RELOAD, variant SAP&RELOAD_ALL, user ID BGDUSER)      00           550          S
15.05.2008 00:30:11 No component system chosen                                                                   URL_GEN_MSGS      031          E
15.05.2008 00:30:11 Job cancelled after system exception ERROR_MESSAGE                                                00           564          A
Please help to resolve this issue.
Thanks in advance.
Regards
Sudip Ghosh

Hi Markus,
Thanks for the reply.
Below is the dump:
======
======
Runtime Errors         DBIF_DSQL2_SQL_ERROR
Date and Time          15.05.2008 06:25:36
Short text
An SQL error occurred when executing Native SQL.
What happened?
The error 3113 occurred in the current database connection "DEFAULT".
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
How to correct the error
Database error text........: "ORA-03113: end-of-file on communication channel"
Database error code........: 3113
Triggering SQL statement...: "FETCH NEXT "
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DBIF_DSQL2_SQL_ERROR" " "
"RSORAVSH" or "RSORAVSH"
"FILL_DBVSE"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "gcbeccd"
Network address...... "10.10.4.158"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 15
Shortdump setting.... "full"
Database server... "gcbeccd"
Database type..... "ORACLE"
Database name..... "RD3"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 5 2008 00:55:24"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.1.0) "
Patch level. 146
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 1117216
EM...... 0
Heap.... 0
Page.... 32768
MM Used. 695792
MM Free. 400816
User and Transaction
Client.............. 000
User................ "BGDUSER"
Language key........ "E"
Transaction......... " "
Transactions ID..... "482B8A4C89F0442BE10000000A0A049E"
Program............. "RSORAVSH"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "RSORAVSH" - in "FILL_DBVSE".
The main program was "RSORAVSH ".
In the source code you have the termination point in line 48
of the (Include) program "RSORAVSH".
The program "RSORAVSH" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "BGDUSER"
Job Number..... 05251100
Source Code Extract
Line
SourceCde
18
INCLUDE STRUCTURE v_system_event_struc.
19
DATA: END OF v_system_event_tab .
20
21
check sy-dbsys(3) = 'ORA' .
22
23
Get the new snapshots
24
25
PERFORM fill_dbvse TABLES v_system_event_tab.
26
27
28
Get the old snapshots from database table MONI
29
30
startday = sy-datum - days_to_keep .
31
32
33
Save new data now (otherwise these data will be selected twice)
34
35
CONCATENATE 'SYSEVENT' sy-datum sy-uzeit INTO   monikey .
36
37
EXPORT sy-datum
38
sy-uzeit
39
v_system_event_tab
40
TO DATABASE moni(db) ID monikey .
41
42
*&      Form FILL_DBVSE
43
44
FORM fill_dbvse TABLES v_system_event_tab.
45
date = sy-datum .
46
time = sy-uzeit .
47
EXEC sql performing append_v_system_event .
>>>>>
select event,
49
total_waits,
50
total_timeouts,
51
time_waited * 10,
52
average_wait * 10
53
into :v_system_event_struc
54
from v$system_event
55
ENDEXEC .
56
ENDFORM.                               " FILL_DBVSE
57
58
59
*&      Form APPEND_V_SYSTEM_EVENT
60
61
FORM append_v_system_event.
62
v_system_event_tab-date = date .
63
v_system_event_tab-time = time .
64
65
MOVE-CORRESPONDING v_system_event_struc TO v_system_event_tab.
66
APPEND v_system_event_tab .
67
ENDFORM.                               " APPEND_V_SYSTEM_EVENT
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
16
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Report for Collecting Data from V$SYSTEM_EVENT Hourly
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080515
SY-UZEIT
062520
SY-XPROG
RSDBRUNT
SY-XFORM
%_INIT_PBO_FIRST
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
2 FORM         RSORAVSH                            RSORAVSH                               48
FILL_DBVSE
1 EVENT        RSORAVSH                            RSORAVSH                               25
START-OF-SELECTION
Chosen variables
Name
Val.
No.       2 Ty.          FORM
Name FILL_DBVSE
SY-REPID
RSORAVSH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545455422222222222222222222222222222222
23F2163800000000000000000000000000000000
V_SYSTEM_EVENT_STRUC
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222222222222222220000000000000000
0000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
%_SPACE
0
0
2
0
SY
###############################################################################T######## ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
No.       1 Ty.          EVENT
Name START-OF-SELECTION
SY-LDBPG
SAPDB__S
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454455522222222222222222222222222222222
31042FF300000000000000000000000000000000
%_DUMMY$$
0000
0000
2222
0000
SY-DBSYS+0(6)
ORA
000
000
454
F21
SYST
###############################################################################T######## ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
V_SYSTEM_EVENT_TAB[]
Table[initial]
V_SYSTEM_EVENT_TAB
00000000000000                                                                ################
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3333333333333322222222222222222222222222222222222222222222222222222222222222220000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
SY-DATUM
20080515
00000000
00000000
33333333
20080515
DAYS_TO_KEEP
30
0001
000E
STARTDAY
00000000
00000000
00000000
33333333
00000000
MONIKEY
0000000000000000000000
0000000000000000000000
2222222222222222222222
0000000000000000000000
SY-UZEIT
062520
000000
000000
333333
062520
SYST-REPID
RSORAVSH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545455422222222222222222222222222222222
23F2163800000000000000000000000000000000
MONI-CLUSTR
0
00
00
MONI
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222220022000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Internal notes
The termination was triggered in function "ExecuteCall"
of the SAP kernel, in line 1190 of the module
"//bas/700_REL/src/krn/runt/abexsql.c#2".
The internal operation just processed is "DSQL".
Internal mode was started at 20080515062520.
Internal call code.........: "[DBDS/NEW DSQL]"
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
(0) 0x4000000003b2b450 CTrcStack + 0x1b0 at dptstack.c:227 [dw.sapRD3_DVEBMGS00]
(1) 0x4000000004d2c470 Z16rabaxCStackSavev + 0x1d0 [dw.sapRD3_DVEBMGS00]
(2) 0x4000000004d32160 ab_rabax + 0x3570 [dw.sapRD3_DVEBMGS00]
(3) 0x40000000047b51e0 Z10abdbdserriPKtiS0_P9DS_HEADERS0_iPv + 0x470 [dw.sapRD3_DVEBMGS00]
(4) 0x4000000003d777f0 Z11ExecuteCallv + 0x11f0 [dw.sapRD3DVEBMGS00]
(5) 0x4000000003d7e7b0 Z8abjdsqlv + 0x1b0 [dw.sapRD3_DVEBMGS00]
(6) 0x400000000402f190 Z8abextriv + 0x440 [dw.sapRD3_DVEBMGS00]
(7) 0x4000000003f53bc0 Z9abxeventPKt + 0x3c0 at abrunt1.c:339 [dw.sapRD3_DVEBMGS00]
(8) 0x4000000003d9f210 Z8abtriggv + 0x110 at abrunt1.c:58 [dw.sapRD3_DVEBMGS00]
(9) 0x4000000003d9ebe0 ab_run + 0xc0 [dw.sapRD3_DVEBMGS00]
(10) 0x4000000001caa820 N_ab_run + 0x20 at dymainstp.c:4739 [dw.sapRD3_DVEBMGS00]
(11) 0x4000000001cb40f0 dynpmcal + 0x3f0 at dymainstp.c:2281 [dw.sapRD3_DVEBMGS00]
(12) 0x4000000001caf260 dynppai0 + 0xcb0 at dymainstp.c:1107 [dw.sapRD3_DVEBMGS00]
(13) 0x4000000001cb1ec0 dynprctl + 0x340 at dymainstp.c:358 [dw.sapRD3_DVEBMGS00]
(14) 0x4000000001c9dff0 dynpen00 + 0xac0 at dymain.c:1628 [dw.sapRD3_DVEBMGS00]
(15) 0x4000000001fea460 Thdynpen00 + 0x510 at thxxhead.c:4830 [dw.sapRD3_DVEBMGS00]
(16) 0x4000000001fb54e0 TskhLoop + 0x5520 at thxxhead.c:3945 [dw.sapRD3_DVEBMGS00]
(17) 0x4000000001faae40 ThStart + 0x460 at thxxhead.c:1164 [dw.sapRD3_DVEBMGS00]
(18) 0x4000000001569ec0 DpMain + 0x5f0 at dpxxdisp.c:1088 [dw.sapRD3_DVEBMGS00]
(19) 0x4000000002c10630 nlsui_main + 0x30 [dw.sapRD3_DVEBMGS00]
(20) 0x4000000002c105c0 main + 0x60 [dw.sapRD3_DVEBMGS00]
(21) 0xc00000000002be30 main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
RSORAVSH
0
30.03.2005
10:21:59
19456
E
1
Prg
SAPMSSY0
1
17.12.2007
15:41:05
92160
E
2
Prg
SAPMSSYD
1
12.09.2006
11:33:31
21504
E
3
Prg
SAPFSYSCALLS
1
09.09.2004
14:18:32
8192
E
4
Prg
RSDBRUNT
0
17.12.2007
16:04:40
254976
E
5
Typ
RSSCR
0
30.03.2005
10:21:45
5120
6
Prg
RSDBSPBL
0
30.03.2005
10:21:58
72704
E
7
Prg
SAPDB__S
0
30.03.2005
10:22:01
19456
E
8
Prg
RSDBSPMC
0
12.09.2006
11:25:01
79872
E
9
Typ
DDSHDESCR
0
03.09.1997
03:05:16
4096
10
Typ
SPPARAMS
0
07.05.1997
13:10:38
2048
11
Prg
SAPLSABE
11
09.09.2004
14:18:36
13312
E
12
Prg
SAPLSECU
12
17.12.2007
15:31:45
87040
E
13
Typ
RSSUBINFO
0
14.10.1999
22:01:03
3072
14
Prg
SAPLSTUP
14
17.12.2007
15:29:58
74752
E
15
Prg
SAPLCNDP
15
11.09.2007
15:24:45
195584
E
16
Prg
SAPLSCNT
16
18.02.2005
14:16:06
30720
E
17
Prg
SAPSHDTV
16
05.01.2005
16:26:16
33792
E
18
Prg
SAPFGUICNTL
1
18.02.2005
14:15:08
24576
E
19
Prg
SAPLOLEA
19
11.09.2007
11:17:30
96256
E
20
Prg
SAPLSGUI
20
17.12.2007
15:41:05
84992
E
21
Prg
SAPLSTTM
21
05.07.2005
13:10:18
69632
E
22
Prg
SAPLSBDC
22
17.12.2007
15:30:54
44032
E
23
Prg
SAPLSFES
23
17.12.2007
16:04:40
260096
E
24
Prg
SAPLTHFB
24
17.12.2007
15:41:05
394240
E
25
Typ
WPINFO
0
26.02.1999
14:49:01
6144
26
Prg
SAPLURFC
26
17.12.2007
15:37:35
22528
E
27
Prg
SAPLSPLUGIN
27
09.09.2004
14:18:36
8192
E
28
Typ
SWCBCONT
0
15.11.2000
17:55:11
3072
29
Typ
OLE_VERBS
0
04.04.1995
16:02:20
2048
30
Typ
OLE_PA
0
04.04.1995
16:02:19
2048
31
Typ
SYST
0
09.09.2004
14:18:12
31744
32
Typ
MONI
0
31.03.2004
16:41:21
5120
Directory of Application Tables
Name                                     Date       Time       Lngth
Val.
Program RSORAVSH
SYST                                     09.09.2004 14:18:12   00004612
\0\0\0\0\0\x0010\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0
MONI                                       . .       : :     00002944
\0\0 \0\0\0\0\0\0\0\0\0\0\0\0\0\0
ABAP Control Blocks (CONT)
Index
Name
Fl
PAR0
PAR1
PAR2
PAR3
PAR4
PAR5
PAR6
Source Code
Line
71
PAR2
03
0000
0014
002B
RSORAVSH
37
73
PAR2
03
0000
0015
002D
RSORAVSH
37
75
PAR2
03
0000
0016
0026
RSORAVSH
37
77
00
0000
RSORAVSH
37
78
PERP
00
0002
RSORAVSH
44
79
PERP
1C
0000
RSORAVSH
44
80
PERP
04
0000
RSORAVSH
44
81
mvqk
10
0005
0044
04EC
RSORAVSH
45
83
mvqk
0C
0005
0054
052E
RSORAVSH
46
85
DSQL
00
0017
RSORAVSH
48
86
DSQL
01
0018
RSORAVSH
48
87
DSQL
04
0025
RSORAVSH
48
>>>>>
DSQL
16
0025
RSORAVSH
48
89
BRAN
05
0004
RSORAVSH
48
90
perf
00
000A
RSORAVSH
48
91
PERP
80
0000
RSORAVSH
48
92
BRAX
00
FFFC
RSORAVSH
48
93
DSQL
23
0000
RSORAVSH
48
94
ENDF
00
0000
RSORAVSH
56
95
00
0000
RSORAVSH
56
===========
===========
Please check and advise.
Also, I am trying to search for the note 6083 in market place, but not getting the same.
Please advise.
Thanks & Regards
Sudip

Transaction log full

Transaction log is full in production system ,when i was tried login into sap system it show the error message 'SNAP_NO_NEW_ENTRIES'.
our system is db2 and AIX ,can any body hlep us step by step procedure for reslove the issue .
For best answer will reward.
Thanks
Imran khan

you have to increase the sum of the logs in order to enlarge the database log...plz do not forget that the log must fit the underlying file system, eg. /db2/<SID>/dir_log..so you might have to increase this as well using SMITTY...
(DB6) [IBM][CLI Driver][DB2/AIX64] SQL0964C The transaction log for the database is full. SQLSTATE=57011
[root] > su - db2<sid>
1> db2 get db cfg for <SID> | grep -i logfilsiz
Log file size (4KB) (LOGFILSIZ) = 16380
2> db2 get db cfg for <SID> | grep -i logprimary
Number of primary log files (LOGPRIMARY) = 20
3> db2 get db cfg for <SID> | grep -i logsecond
Number of secondary log files (LOGSECOND) = 40
so we have log file of max. 16.380 * 4.096 * 60 = 4.025.548.800 bytes (about 4 gb)...this needs to be increased by increasing either LOGPRIMARY and/or LOGSECONDARY...(assuming that your logfile size is 16kb...query db2 for your size!)
4> db2 update db cfg for <SID> using logsecond 80 immediate
DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
SQL1363W One or more of the parameters submitted for immediate modification
were not changed dynamically. For these configuration parameters, all
applications must disconnect from this database before the changes become
effective.
5> db2 get db cfg for <SID> | grep -i logprimary
Number of primary log files (LOGPRIMARY) = 20
6> db2 get db cfg for <SID> | grep -i logsecond
Number of secondary log files (LOGSECOND) = 80
7> db2stop
02/20/2007 09:17:12 0 0 SQL1064N DB2STOP processing was successful.
SQL1064N DB2STOP processing was successful.
8> db2start
02/20/2007 09:17:19 0 0 SQL1063N DB2START processing was successful.
SQL1063N DB2START processing was successful.
-> plz keep in mind that the sap system needs to be down when re-starting db2...
check via snapshot:
9> db2 get snapshot for database on <SID>
Log space available to the database (Bytes)= 2353114756 (= 2.353 MB)
Log space used by the database (Bytes) = 4329925244 (= 4.329 MB)
Maximum secondary log space used (Bytes) = 2993640963
Maximum total log space used (Bytes) = 4330248963
Secondary logs allocated currently = 46
Appl id holding the oldest transaction = 9
so now our log is about 6.5 gb ...see sapnote 25.351 for details...
GreetZ, AH

What are the side effects of setting "_object_statistics=false"?

Hi,
On a 10.2.0.3.0, due to frequent ORA-04031 errors, we have been recommended to set objectstatistics=false in init.ora and bounce the database.
Metalink Bug ID: 3519807
Going through the available documentation on net, I found that this parameter would have same effect as setting STATISTICS_LEVEL=BASIC or even worse.
Documentation (for statistics_level) says following options are affected.
* Automatic Workload Repository (AWR) Snapshots
* Automatic Database Diagnostic Monitor (ADDM)
* All server-generated alerts
* Automatic SGA Memory Management
* Automatic optimizer statistics collection
* Object level statistics
* End to End Application Tracing (V$CLIENT_STATS)
* Database time distribution statistics (V$SESS_TIME_MODEL and V$SYS_TIME_MODEL)
* Service level statistics
* Buffer cache advisory
* MTTR advisory
* Shared pool sizing advisory
* Segment level statistics
* PGA Target advisory
* Timed statistics
* Monitoring of statistics
We have daily schema statistics gathering schedule in place so I feel query performance should not be affected (of course, this is my assumption).
I just wanted to know what else would be affected due to this.
Thanks in advance.
Regards,

Please let me know your ideas/inputs.

Snapshot of database

Similar Messages

Maybe you are looking for