on 11-19-2013 11:27 AM
Hi all,
We we trying to change logical name for one of sap server.
The job RBDLSMAP was stop with: Error
Error Text of the Database: "ORA-01555: snapshot too old: rollback segment number 1 with name "_SYSSMU1_3778823473$" too small":
Category Installation Errors
Runtime Errors DBIF_RSQL_SQL_ERROR
Except. CX_SY_OPEN_SQL_DB
Date and Time 18.11.2013 22:55:27
Short text
SQL error 1555 when accessing table "VBRP".
What happened?
Error Text of the Database: "ORA-01555: snapshot too old: rollback segment
number 1 with name "_SYSSMU1_3778823473$" too small"
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
.
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
.
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caugh
in
procedure "BDLS_CONVERT_ARG" "(FUNCTION)", nor was it propagated by a RAISIN
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Error Text of the Database: "ORA-01555: snapshot too old: rollback segment
number 1 with name "_SYSSMU1_3778823473$" too small"
How to correct the error
Internal call code.........: "[RSQL/READ/VBRP ]"
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
Any help for this error
Thanks
reza
Check these links
http://scn.sap.com/thread/523152
http://www.dba-oracle.com/t_ora_01555_snapshot_old.htm
Also check this SAP note
185822 - ora-1555 - cause and action
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ejersbo
I would look further into the process you are currently running that is causing this dump rather than the oracle error itself as you may find it misleading.
It appears you are running BDLS to convert the logical system of table VBRP. This error indicates that the conversion process is running for a considerable amount of time and due to the potential volume of changing data within that table the rollback process cant guarantee its consistency over a great length of time so I stops the transaction.
I would look at speeding up the BDLS process to reduce the runtime. by performing the following steps. You could also perform this activity at times of lower user activity.
1, Run BDLS in test mode only for table VBRP.
2. Create a separate tablespace - PSAPSR3BDLS
3. Create an new index on VBRP
CREATE INDEX SAPSR3."VBRP~ZB" ON SAPSR3.VBRP (MANDT, LOGSYS) NOLOGGING TABLESPACE PSAPSR3BDLS PARALLEL;
4. Alter index
ALTER INDEX SAPSR3."VBRP~ZB" NOPARALLEL;
5. Analyze index
ANALYZE INDEX SAPSR3."VBRP~ZB" ESTIMATE STATISTICS SAMPLE 2 PERCENT;
6. Run the BDLS for VBRP.
Thanks
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ejersbo,
Please check this note 3807 - Error messages regarding rollback and undo segments
section 3,
also, post us your database and sap release and version.
regards
kartik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.