FDM Locations Lock Error in System 11

All,
We've just migrated our 9.2 system to 11.1.1.3.00 . When we try to lock all locations (Current Category Period), it's always throwing an error saying "Multiple-step operation generated errors. Check each status value". We're using the admin id which is having "Administartor" access and grant access to all locations is checked.
This was working fine in system 9.2. We have total 60 locations available in FDM. We've raised one ticket with Oracle but they are taking too much time to respond. If any of you had experienced this issue before, please let me know.
Thanks in advance!!

This is more than likely a Oracle Client issue. What oracle Client is installed and what db version is being used? What is your cursor sharing db parameter set to? Have you had the DBA run a trace when this process was performed? This is going to be something more complicated than a forum discussion. I would continue to work through the sr process.

Similar Messages

System Lock error : Inform System administrator

Dear all,
One of the SAP user got this (System Lock error : Inform System administrator) error , while doing posting .
Kindly advise

Hi,
Check for any lock entries in the TA SM12 and then have a look at the note 13907 System error in the block handler, overflow lock table.
Hope this helps.
_Varadhu...

FBRA: System lock error inform system administrator

While trying to reset a document transaction code FBRA, am getting the error message "System lock error inform your system administrator" when I hit the save button.
how do i solve this?
You help is much obliged.
ogutu

Dear Ogutu,
the F5288 error message (System lock error: inform system Administrator)
appears to be caused by a table overflow as it takes place with a very
large document ie. xxxx line items. As all the items must be locked when
transaction FBRA is performed, there is not enough space in the lock
table.
Please extend the profile-parameter "enque/table_size", as per note
13907, 487347 which I have attached, in order to overcome this problem.
You have to change a parameter.
Then please remember to restart the server after extend the
profile-parameter "enque/table_size", as per note note 13907.
If you already did it and nothing changed, please increase the parameter
again.
Please be aware that You have also to implement the solution described
in note 487347. There is not only correction code, there is also some
steps to do in order to solve the incident (manual changes have to be
done in SE93):
1. Implement the corrections. The corrections are not contained in the
     SAP Standard System. See Note 170183.
2. Use Transaction SE93 to create the parameter transaction FBRA_LOAC
     referring to transaction FBRA. In addition to the descriptive text
     'Reset Cleared Items with Account Block', you have to enter the
     value FBRA in the 'Transaction' field.
3. In problematic cases, use transaction FBRA_LOAC to reset cleared
     items. The transaction is not designed to replace the existing
     transaction FBRA. The transaction only provides the option to reset
     cleared items in case of an overflow of the lock table.
I hope this helps.
Mauri

FDM Multi-load error in system 11

Hi All,
I'm getting an error while loading the data into HFM through FDM in system 11. We just migrated our system from 9.2, and this used to work fine in the old system. As per the error message, it creates "PER" instead of "PERIODIC" in the new system 11 output file provided below. And for the [MISSING_VALUE], I think we'll have to add "* to [NONE]" maps in other dimensions. But I'm clueless on the "PER" value, can you share your thought please!! Thanks in advance!
FDM generated the file in system 9.2:
!Data
!Period=February...January
!Column_Order = Scenario,Year,View,Entity,Value,Account,ICP,Custom1,Custom2,Custom3,Custom4
GUIDANCEQ3;2010;PERIODIC;BAWOS;<Entity Currency>;999010;[ICP None];SALESCOGSPCS;0050;[None];[None];;9440;;;;;;;;;;
FDM generated the file in system 11:
!Data
!Period=February...January
!Column_Order = Scenario,Year,View,Entity,Value,Account,ICP,Custom1,Custom2,Custom3,Custom4
GUIDANCEQ4;2010;PER;BAWOS;<Entity Currency>;999010;[MISSING_VALUE];SALESCOGSPCS;0050;[MISSING_VALUE];[MISSING_VALUE];;9440;;;;;;;;;;
I'm using the below header in the data file for multi-load:
WOS
GuidanceQ4
02/28/2010
12
R,R,0,,,,Y,N,,PERIODIC
c,ud1,ud2,A,v,v,v,v,v,v,v,v,v,v,v,v

There are KM articles that address these 2 issues. Likewise there are several forum postings that address these exact issues. Did you do a search of the forum or support.oracle.com?
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=PROBLEM&id=840319.1
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=PROBLEM&id=1055134.1

System Lock error

Hello,
We get an error "System lock error: Inform system Administrator" when we use the transaction FBRA. This error is just occurring for one particular FI document. Any idea why this could be happenning? Is this a Basis issue?
Any help will be appreciated.
Thanks,
ALAM.

look like basis issue only
ask basis team if enqueu overflow is happening
can you find any long message of this error
Samrat

System Lock Error while reset & reversing the cleared document - FBRA

Hi Experts,
Currently using t-code FBRA, when user trying to reset & reverse the cleared document , they are facing "System Lock Error". We have analyzed on this issue and found SAP note no. u201C487347 u2013FBRA: Overflow of the lock table in production systemu201D . After implementation of this note, SAP has created one new transaction code, FBRA_LOAC.
However, when we tried to reset & reverse the cleared document using t-code FBRA_LOAC, we face the same error.
Can you help me to resolve this issue ?
Thanks in advance.
Regards,
Manish

Hi:
We once faced these issue and got it resolved by extending parameter after extending the profile-parameter "enque/table_size", as per note note 13907. Do not forget the restart the server after extension.
Regards

System Locking Error - WebAS 6.40 ABAP

My Netweaver 6.40 ABAP edition is now up and running. License is installed. I had to resolve an index-problem in the database layer by recreating a corrupt index via DBMCLI, but now the database seems to be fine.
But I still can't "lock" anything. When I e.g. try to change client settings in SCC4, I get an error message:
"System error: Unable to lock table/view T000".
When I try to activate a service in SICF, I get "System locking error" (SR053). It seems that the enqueue server doesn't work.
SM12 (Lock entries) diagnostics say: "System error during lock operation. Execute diagnostics in SM12" (03113). Interesting message, but not much help as I just did execute the diagnostics in SM12.
The current workprocess configuration is:
rdisp/wp_no_dia=2
rdisp/wp_no_btc=1
rdisp/wp_no_vb=0
rdisp/wp_no_vb2=0
rdisp/wp_no_enq=0
rdisp/wp_no_spo=0
Which is the default. I also tried
rdisp/wp_no_dia=2
rdisp/wp_no_btc=0
rdisp/wp_no_vb=0
rdisp/wp_no_vb2=0
rdisp/wp_no_enq=1
rdisp/wp_no_spo=0
but that did not help.
My hostname is NLVEHVHSE1NB272 (15 characters!). 6.10 could not be installed on a computer with such a long name, but 6.40 can.
My rdisp/enqname is "NLVEHVHSE1NB272_NSP_", where I would expect "NLVEHVHSE1NB272_NSP_00".
Does anybody know what the reason for my locking problems could be ? Thanks !

Hi Ralf
I had an identical problem and have been able to solve it by shortening the host name to less than 13 characters.
OSS Notes 611361 and 23538 may he of help
Cheers
Grahame

System Lock error:Inform your system administrator

dears,
i receive this error message (System Lock error:Inform your system administrator) while doing Sales order or , & MIGO. can you please help out

Hi,
This is not an Unicode issue, but anyway check this note:
13907 - System error in the block handler, overflow lock table.
Marco

BAPI_REQUIREMENTS_CREATE gives System Lock Error

Hi All,
When I am creating the Material Requirements Plan using BAPI_REQUIREMENTS_CREATE then everything works fine but at random intervals for a bunch of materials it is giving System Lock Error message.
so I did like this
loop at..
BAPI_REQUIREMENTS_CREATE
BAPI_TRANSACTION_COMMIT
dequeue_all. (function module)
endloop.
Still didnt help.
Please suggest me any other reasons..

Hi
Refer This Link
Re: BAPI for MD61
Ranga

Restore using TSPITR Results Dead lock error

This is the step is followed but i am getting deadlock error .please give your valuable suggestion .
Product Used:oracle 11g in linux environmnet
1)Before taking backup get SCN number for restore.
Command applied: Select current_scn from v$database;
2)running Full backup of database
Command applied:
configure controlfile autobackup on;
backup database;
CROSSCHECK BACKUP;
exit;
3)Running level 0 incremental backup
Command applied:
BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 0 TAG ='WEEKLY' TABLESPACE TEST;
exit;
3) Running level 1 incremental backup
Command applied:
BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 1 TAG ='DAILY' TABLESPACE TEST;
4)Before Restore(TSPITR) following procedure are applied under sysdba privilege
Command applied:
SQL 'exec dbms_backup_restore.manageauxinstance ('TSPITR',1)';
5)TSPITR Restore command
Command applied:
run
SQL 'ALTER TABLESPACE TEST OFFLINE'
RECOVER TABLESPACE TEST UNTIL SCN 1791053 AUXILIARY DESTINATION '/opt/oracle/base/flash_recovery_area';
SQL 'ALTER TABLESPACE TEST ONLINE';
and i tried with this option also(the same error i was getting)
Command applied:
run
SQL 'ALTER TABLESPACE TEST OFFLINE';
SET UNTIL SCN 1912813;
RESTORE TABLESPACE TEST ;
RECOVER TABLESPACE TEST UNTIL SCN 1912813 AUXILIARY DESTINATION '/opt/oracle/base/flash_recovery_area';
SQL 'ALTER TABLESPACE TEST ONLINE';
The follwing error i get for above mentioned restore command
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Aug 17 18:11:18 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: NEW10 (DBID=2860680927)
RMAN> run
2> {
3> SQL 'ALTER TABLESPACE TEST OFFLINE';
4> RECOVER TABLESPACE TEST UNTIL SCN 1791053 AUXILIARY DESTINATION '/opt/oracle/base/flash_recovery_area';
5> SQL 'ALTER TABLESPACE TEST ONLINE';
6> }
7>
using target database control file instead of recovery catalog
sql statement: ALTER TABLESPACE TEST OFFLINE
Starting recover at 17-AUG-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=404 device type=DISK
RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point-in-time
List of tablespaces expected to have UNDO segments
Tablespace SYSTEM
Tablespace UNDOTBS1
Creating automatic instance, with SID='BkAq'
initialization parameters used for automatic instance:
db_name=NEW10
db_unique_name=BkAq_tspitr_NEW10
compatible=11.2.0.0.0
db_block_size=8192
db_files=200
sga_target=280M
processes=50
db_create_file_dest=/opt/oracle/base/flash_recovery_area
log_archive_dest_1='location=/opt/oracle/base/flash_recovery_area'
#No auxiliary parameter file used
starting up automatic instance NEW10
Oracle instance started
Total System Global Area 292933632 bytes
Fixed Size 1336092 bytes
Variable Size 100666596 bytes
Database Buffers 184549376 bytes
Redo Buffers 6381568 bytes
Automatic instance created
Running TRANSPORT_SET_CHECK on recovery set tablespaces
TRANSPORT_SET_CHECK completed successfully
contents of Memory Script:
# set requested point in time
set until scn 1791053;
# restore the controlfile
restore clone controlfile;
# mount the controlfile
sql clone 'alter database mount clone database';
# archive current online log
sql 'alter system archive log current';
# avoid unnecessary autobackups for structural changes during TSPITR
sql 'begin dbms_backup_restore.AutoBackupFlag(FALSE); end;';
executing Memory Script
executing command: SET until clause
Starting restore at 17-AUG-10
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=59 device type=DISK
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /opt/oracle/base/flash_recovery_area/NEW10/autobackup/2010_08_17/o1_mf_s_727280767_66nmo8x7_.bkp
channel ORA_AUX_DISK_1: piece handle=/opt/oracle/base/flash_recovery_area/NEW10/autobackup/2010_08_17/o1_mf_s_727280767_66nmo8x7_.bkp tag=TAG20100817T142607
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/opt/oracle/base/flash_recovery_area/NEW10/controlfile/o1_mf_66o0wsh8_.ctl
Finished restore at 17-AUG-10
sql statement: alter database mount clone database
sql statement: alter system archive log current
sql statement: begin dbms_backup_restore.AutoBackupFlag(FALSE); end;
contents of Memory Script:
# set requested point in time
set until scn 1791053;
# set destinations for recovery set and auxiliary set datafiles
set newname for clone datafile 1 to new;
set newname for clone datafile 8 to new;
set newname for clone datafile 3 to new;
set newname for clone datafile 2 to new;
set newname for clone datafile 9 to new;
set newname for clone tempfile 1 to new;
set newname for datafile 7 to
"/opt/oracle/base/oradata/NEW10/test01.dbf";
# switch all tempfiles
switch clone tempfile all;
# restore the tablespaces in the recovery set and the auxiliary set
restore clone datafile 1, 8, 3, 2, 9, 7;
switch clone datafile all;
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
renamed tempfile 1 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_temp_%u_.tmp in control file
Starting restore at 17-AUG-10
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00001 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00008 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00003 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_undotbs1_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00002 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00009 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_%u_.dbf
channel ORA_AUX_DISK_1: reading from backup piece /opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnndf_TAG20100817T140128_66nl7174_.bkp
channel ORA_AUX_DISK_1: piece handle=/opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnndf_TAG20100817T140128_66nl7174_.bkp tag=TAG20100817T140128
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:02:45
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00007 to /opt/oracle/base/oradata/NEW10/test01.dbf
channel ORA_AUX_DISK_1: reading from backup piece /opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnnd0_WEEKLY_66nl9m8k_.bkp
channel ORA_AUX_DISK_1: piece handle=/opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnnd0_WEEKLY_66nl9m8k_.bkp tag=WEEKLY
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:06:55
Finished restore at 17-AUG-10
datafile 1 switched to datafile copy
input datafile copy RECID=6 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_66o0x1sf_.dbf
datafile 8 switched to datafile copy
input datafile copy RECID=7 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_66o0x1r9_.dbf
datafile 3 switched to datafile copy
input datafile copy RECID=8 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_undotbs1_66o0x1vr_.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=9 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_66o0x1vj_.dbf
datafile 9 switched to datafile copy
input datafile copy RECID=10 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_66o0x1rs_.dbf
contents of Memory Script:
# set requested point in time
set until scn 1791053;
# online the datafiles restored or switched
sql clone "alter database datafile 1 online";
sql clone "alter database datafile 8 online";
sql clone "alter database datafile 3 online";
sql clone "alter database datafile 2 online";
sql clone "alter database datafile 9 online";
sql clone "alter database datafile 7 online";
# recover and open resetlogs
recover clone database tablespace "TEST", "SYSTEM", "UNDOTBS1", "SYSAUX" delete archivelog;
alter clone database open resetlogs;
executing Memory Script
executing command: SET until clause
sql statement: alter database datafile 1 online
sql statement: alter database datafile 8 online
sql statement: alter database datafile 3 online
sql statement: alter database datafile 2 online
sql statement: alter database datafile 9 online
sql statement: alter database datafile 7 online
Starting recover at 17-AUG-10
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting incremental datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00007: /opt/oracle/base/oradata/NEW10/test01.dbf
channel ORA_AUX_DISK_1: reading from backup piece /opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnnd1_DAILY_66nmf6qs_.bkp
channel ORA_AUX_DISK_1: piece handle=/opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnnd1_DAILY_66nmf6qs_.bkp tag=DAILY
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
starting media recovery
archived log for thread 1 with sequence 39 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_39_66nmc1dg_.arc
archived log for thread 1 with sequence 40 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_40_66nmcfw4_.arc
archived log for thread 1 with sequence 41 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_41_66nmcwcf_.arc
archived log for thread 1 with sequence 42 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_42_66nmddbw_.arc
archived log for thread 1 with sequence 43 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_43_66o0wyys_.arc
archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_39_66nmc1dg_.arc thread=1 sequence=39
archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_40_66nmcfw4_.arc thread=1 sequence=40
archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_41_66nmcwcf_.arc thread=1 sequence=41
archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_42_66nmddbw_.arc thread=1 sequence=42
archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_43_66o0wyys_.arc thread=1 sequence=43
media recovery complete, elapsed time: 00:00:50
Finished recover at 17-AUG-10
database opened
contents of Memory Script:
# make read only the tablespace that will be exported
sql clone 'alter tablespace TEST read only';
# create directory for datapump import
sql "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/opt/oracle/base/flash_recovery_area''";
# create directory for datapump export
sql clone "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/opt/oracle/base/flash_recovery_area''";
executing Memory Script
sql statement: alter tablespace TEST read only
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/opt/oracle/base/flash_recovery_area''
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/opt/oracle/base/flash_recovery_area''
Performing export of metadata...
EXPDP> Starting "SYS"."TSPITR_EXP_BkAq":
EXPDP> Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
EXPDP> Processing object type TRANSPORTABLE_EXPORT/TABLE
EXPDP> Processing object type TRANSPORTABLE_EXPORT/GRANT/OWNER_GRANT/OBJECT_GRANT
EXPDP> Processing object type TRANSPORTABLE_EXPORT/INDEX
EXPDP> Processing object type TRANSPORTABLE_EXPORT/CONSTRAINT/CONSTRAINT
EXPDP> Processing object type TRANSPORTABLE_EXPORT/INDEX_STATISTICS
EXPDP> Processing object type TRANSPORTABLE_EXPORT/TRIGGER
EXPDP> Processing object type TRANSPORTABLE_EXPORT/TABLE_STATISTICS
EXPDP> Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PLUGTS_BLK
EXPDP> Master table "SYS"."TSPITR_EXP_BkAq" successfully loaded/unloaded
EXPDP> ******************************************************************************
EXPDP> Dump file set for SYS.TSPITR_EXP_BkAq is:
EXPDP> /opt/oracle/base/flash_recovery_area/tspitr_BkAq_82690.dmp
EXPDP> ******************************************************************************
EXPDP> Datafiles required for transportable tablespace TEST:
EXPDP> /opt/oracle/base/oradata/NEW10/test01.dbf
EXPDP> Job "SYS"."TSPITR_EXP_BkAq" successfully completed at 18:25:02
Export completed
contents of Memory Script:
# shutdown clone before import
shutdown clone immediate
# drop target tablespaces before importing them back
sql 'drop tablespace TEST including contents keep datafiles';
executing Memory Script
database closed
database dismounted
Oracle instance shut down
sql statement: drop tablespace TEST including contents keep datafiles
Removing automatic instance
shutting down automatic instance
target database instance not started
Automatic instance removed
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_temp_66o1k480_.tmp deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/onlinelog/o1_mf_3_66o1k0mg_.log deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/onlinelog/o1_mf_2_66o1jyt4_.log deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/onlinelog/o1_mf_1_66o1jx3w_.log deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_66o0x1rs_.dbf deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_66o0x1vj_.dbf deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_undotbs1_66o0x1vr_.dbf deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_66o0x1r9_.dbf deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_66o0x1sf_.dbf deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/controlfile/o1_mf_66o0wsh8_.ctl deleted
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/17/2010 18:25:36
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of sql command on default channel at 08/17/2010 18:25:25
RMAN-11003: failure during parse/execution of SQL statement: drop tablespace TEST including contents keep datafiles
ORA-00604: error occurred at recursive SQL level 1
ORA-00060: deadlock detected while waiting for resource
Recovery Manager complete.
please give your valuable suggestion .It should be more helpful for us.
Edited by: user10750009 on Aug 20, 2010 1:07 AM
Edited by: user10750009 on Aug 20, 2010 1:15 AM

I want TSPITR ,during this operation i faced this deadlock error.
Before that we faced roll backsegment error for that we applied follwing workaround .
If i applied follwing workaround before every backup and restore .i didn't get any error .all things went successful.
spool /tmp/Createtest.log
connect / as sysdba
REM Perform startup in case we are still down
ALTER SYSTEM SET PROCESSES=500 SCOPE=SPFILE;
SHUT IMMEDIATE;
STARTUP MOUNT EXCLUSIVE;
ALTER DATABASE ARCHIVELOG;
ARCHIVE LOG START;
ALTER DATABASE OPEN;
connECT / as sysdba;
alter system set undo_management = MANUAL scope=spfile;
shutdown immediate;
startup;
Connect / as sysdba;
DROP TABLE TEST123;
create table test123 (t1 number, t2 varchar2(10));
begin
for i in 1.. 300000 loop
insert into test values (i,'AAAAAAAAAA');
end loop;
end;
delete test123;
commit;
alter system set undo_management = auto scope=spfile;
shutdown immediate ;
startup ;
The above workaround we applied before creating tablespace and datafile ,after that we face some dead lock error while restore TSPITR .Did you need any more information
Edited by: user10750009 on Aug 20, 2010 1:12 AM

Error: Source system already exists. Message no. RSAR201. Points rewarded.

Error: Source system already exists. Message no. RSAR201
We have installed a BI 7.0 system recently and I am setting up the server to connect to SAP ERP.
In TA SM59 a connection to the SAP ERP has been established. The Remote Logon is OK, (meaning clicking it nothing happens). The Connection Test is OK.
According to the Best Practices paper: B84: BI Connectivity (B84)
http://help.sap.com/bp_biv170/BBLibrary/documentation/B84_BB_ConfigGuide_EN_DE.doc
I have done the following:
In TA RSA1
1.     Choose Modeling.
2.     Choose Source Systems.
3.     Select SAP in the window on the right.
4.     Choose the Context menu (right mouse click).
5.     Choose Create.
6.     Make the following entries:
Available destination: (The above tested connection)
Background user in source system: RFCUSER (I created the user in ERP according to step 1.4 in B84)
Password for source system: *****
Background user in BI: RFCUSER (I created the user in BI according to step 1.4 in B84)
Password for BI user: *****
8.     In the dialog box Please log on as an administrator in the following screen choose Continue.
9.     Log on to the Source System with your administrator user. Choose the correct client.
10.     On the dialog box New Source System Connection choose Continue.
THEN I GET THE ERROR:
Source system already exists.
Message no. RSAR201
What is wrong? I cannot locate any SAP notes to help on this problem.
Best regards,
Carsten Pold

Hello Carsten,
just some guessing at this point...
a)
Is the connection really new? For example, was there another system connected to that ERP, maybe with the same logical name? Or was any of the two systems copied from another system?
b)
Authorisations issues in this process may result in strange error messages. Make sure that the admin user in step 9 really has SAP_ALL. There are a lot of complex activities that this user must be able to do (ALE management, RFC access etc.). To exclude issues with the RFCUSER users: If possible, give them SAP_ALL, too. Of course only temporarily for testing.
c)
I normally don't use existing RFC destinations. Usually, I let the system create those, too. So maybe it makes a difference if you remove the RFC destinations on both sides and try again. In that case, you will of course have to provide the RFC details when creating the source system connection...
I hope this brings you forward a little...
Regards,
Christian!

Transaction CO Through-postings from FI has been locked Error on Assets

Hallo,
We are on ECC 6.0 EHP5 SRM 5.0 EHP1 SAPKIBKT18
We have the following problem. When we want to confirm in SRM PO's which are booked on an Asset the following error occurs:
System status INCM is active (Confirmation 187950)
Transaction CO Through-postings from FI has been locked (Item 1)
We don't have the error when confirming a Purchase order created on a Cost Center or WBS Element and it only occurs in our productive system. We have checked the following
CO through posting open and/or locked and they are ok (Confirmation on Cost Center and WBS Element works so it should be)
The master data of the PO. Can't see anything there
Master data of the Assets
Autoriation of users who are logged in and the RFC users
We cannot seem to find the problem maybe some of you have encountered this ?
Thanks!

Hi,
Please see below for more inputs
http://forums.sdn.sap.com/thread.jspa?messageID=5330802#5330802
http://forums.sdn.sap.com/thread.jspa?messageID=8874880#8874880
http://forums.sdn.sap.com/thread.jspa?messageID=8646493#8646493
Regards,
Nikhil

Whitespace is not allowed at this location. Error while running CP using RDF with XML

Hi All,
I am using RDF report with output type as XML. It have following parameters:
1. Organization Name,
2. Invoice No From
3. Invoice No To
4. Date From
5. Date To
I had developed an RTF and registered that in Oracle Applications. The output comes in Excel file.
When I used to run report using Invoice Number From and Invoice Number To the report is giving normal excel output.
But when I am running using parameters Date From and Date To then XML output is coming after viewing output in CP Output button.
I downloaded that xml file. It is invalid as in the last of xml file it is showing following error message
"Whitespace is not allowed at this location".
Please let me know how can I resolve this problem.
Thanks in advance..
Regards
Sandip

my xml file looks like this....

<XX_ITEM_LOADING>
<LIST_G_BLANKET_NUMBER>
    <G_BLANKET_NUMBER>
      <CUSTOMER>SPS PVT LTD</CUSTOMER>
      <INVOICE_NO>17356</INVOICE_NO>
      <INVOICE_DATE>20-JUL-13</INVOICE_DATE>
      <BUYER_REF>56780YP</BUYER_REF>
      <ITEM_DESCRIPTION>XXCSD</ITEM_DESCRIPTION>
      <NUM_OF_BEANS></NUM_OF_BEANS>
      <CARIRER></CARIRER>
      <SHIP_METHOD_CODE>UK568</SHIP_METHOD_CODE>
      <MODE_OF_TRANSPORT>ROAD</MODE_OF_TRANSPORT>
      <ASSEABLE_VALUE>1134534</ASSEABLE_VALUE>
      <QUANTITY>149</QUANTITY>
      <SOLD_TO>SPS PVT LTD</SOLD_TO>
      <TAN_NO></TAN_NO>
      <ST_REG_NO>943481</ST_REG_NO>
      <EC_CODE></EC_CODE>
      <TERMS>30 NET</TERMS>
      <CUST_PO_NUMBER></CUST_PO_NUMBER>
      <DESTINATION>LONDON</DESTINATION>
      <CP_DAYS>3</CP_DAYS>
    </G_BLANKET_NUMBER>
XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
Whitespace is not allowed at this location. Error processing resource 'file:///C:/Users/sys/Downloads/cp_output_date_range....
      <SOLD_TO>DKSP TECHNOLOGIES & ENGG(A DIV. OF PARROT SYSTEM LTD.)</SOLD_TO>
_METHOD_CODE>

Gets error "-17502; System Level Exception" while running the custom Step in NI TestStnad 2010

I have a custom teststand step which works like For loop in TestStand. Previously I was using LV 2009 and NI TestStand 4.2.1 and this step was working fine. Recently I upgraded my system to LV 2010 and TestStand 2010, since that it is not working.
When I run the step it gives error "-17502; System Level Exception". I have attached error screenshot.
I am using NIFlowControl.dll in this step.
Please do the needful.
Attachments:
System Levle Exception error.JPG ‏25 KB

The source code for NIFlowControl.dll ships with TestStand. Did you perhaps
1) modify the code and rebuild this dll in teststand 4.2.1, but did not move your changes into the 2010 version and recompile the 2010 version?
Or
2) Move your 4.2.1 version of this dll to 2010 in which case it might be missing important code that exists only in the 2010 version. It's best to redo your code changes to the 2010 version and recompile that if needed.
Also ideally your modified version of NIFlowControl.dll should be located in the teststand public directory rather than the program files directory.
-Doug

Error "602" System error: AK Datapart too short

Hi all,
Ok, I have looked just about everywhere for an answer to this but to no avail...I even tried under a few rocks we have laying around.
Anyway here it is:
While running a compression in BW we get Error "602" System error: AK Datapart too short.
This is happening while doing a select statement during the compression of the infocube. It does not happen all the time, just kind like when ever it feels like. The only note I could find in OSS was one about Live Cache and it does not seem to apply.
Here is the dump which I really hate doing this, but it gives all the info needed :
untime Error          DBIF_DSQL2_SQL_ERROR
Except.                CX_SY_NATIVE_SQL_ERROR
Date and Time          08/15/2007 12:23:09
ShrtText
An SQL error occurred when executing Native SQL.
What happened?
Error "-602" occurred in the current database connection "DEFAULT".
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
How to correct the error
Database error text........: "System error: AK Datapart too short"
Database error code .......: "-602"
Triggering SQL statement...: "INSERT INTO "/BIC/EZPSD_C03" ( "KEY_ZPSD_C03P",
"KEY_ZPSD_C03T", "KEY_ZPSD_C03U", "KEY_ZPSD_C031", "KEY_ZPSD_C032",
"KEY_ZPSD_C033", "KEY_ZPSD_C034", "/BIC/ZNET_ASP" ) SELECT ? ,
F."KEY_ZPSD_C03T", F."KEY_ZPSD_C03U", F."KEY_ZPSD_C031", F."KEY_ZPSD_C032","
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_DSQL2_SQL_ERROR" CX_SY_NATIVE_SQL_ERRORC
"GP31VIZWJDTT90894L1IA5YAC7G" or "GP31VIZWJDTT90894L1IA5YAC7G"
"TRANSFER_ALL"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
The exception must either be prevented, caught within the procedure
"TRANSFER_ALL"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "sdcbw03"
Network address.......... "10.64.18.76"
Operating system......... "Linux"
Release.................. "2.6.9-55.ELsmp"
Hardware type............ "x86_64"
Character length......... 16 Bits
Pointer length........... 64 Bits
Work process number...... 21
Short dump setting....... "full"
Database server.......... "sdcbw03"
Database type............ "ADABAS D"
Database name............ "BWP"
Database owner........... "SAPBWP"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Nov 5 2006 19:46:34"
Created in............... "Linux GNU SLES-9 x86_64 cc3.3.3"
Database version......... "SAPDB 7.5.0.030 "
Patch level.............. "156"
Patch text............... " "
Supported environment....
Database................. "MaxDB 7.5.0"
SAP database version..... "640"
Operating system......... "Linux 2.6"
Memory usage.............
Roll..................... 16192
EM....................... 20949280
Heap..................... 0
Page..................... 24576
MM Used.................. 9235016
MM Free.................. 3331560
SAP Release.............. "640"
User and Transaction
Client.............. 011
User................ "ALEREMOTE"
Language key........ "E"
Transaction......... " "
Program............. "GP31VIZWJDTT90894L1IA5YAC7G"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "GP31VIZWJDTT90894L1IA5YAC7G" in
"TRANSFER_ALL".
The main program was "RSPROCESS ".
The termination occurred in line 573 of the source code of the (Include)
program "GP31VIZWJDTT90894L1IA5YAC7G"
of the source code of program "GP31VIZWJDTT90894L1IA5YAC7G" (when calling the
editor 5730).
The program "GP31VIZWJDTT90894L1IA5YAC7G" was started as a background job.
Job name........ "BI_PROCESS_COMPRESS"
Job initiator... "ALEREMOTE"
Job number...... 12185102
Processing was terminated because the exception "CX_SY_NATIVE_SQL_ERROR"
occurred in the
procedure "TRANSFER_ALL" "(FORM)" but was not handled locally, not declared in
the
RAISING clause of the procedure.
The procedure is in the program "GP31VIZWJDTT90894L1IA5YAC7G ". Its source code
starts in line 557
of the (Include) program "GP31VIZWJDTT90894L1IA5YAC7G ".
Source Code Extract
Line
SourceCde
543
ENDIF.
544
545
COMMIT WORK.   " commit and close cursors
546
547
l_str = i_max_requid.
548
PERFORM msg_append(saplrscondense)
549
USING    'S' '355' l_str space space space
550
CHANGING c_t_msg.
551
552
ENDFORM.                               " CONDENSE_FACTTABLE_NEW
553
554
555
     Form TRANSFER_ALL
556
557
FORM TRANSFER_ALL USING i_ref_update       TYPE rs_bool
558
i_pdimid           TYPE I
559
i_pdimid_ref_point TYPE rsd_sid
560
i_pdimid_normal    TYPE rsd_sid
561
i_recordtp         TYPE rsd_sid
562
CHANGING e_ref_ins_cnt TYPE I
563
e_ins_cnt     TYPE I
564
c_t_msg       TYPE rs_t_msg.
565
566
CALL FUNCTION 'RSDU_INFOCUBE_INDEXES_DROP'
567
EXPORTING
568
I_INFOCUBE = 'ZPSD_C03'
569
I_FACTTAB = '/BIC/EZPSD_C03'.
570
571
572
EXEC SQL.
>>>>>
INSERT INTO "/BIC/EZPSD_C03"
574
( "KEY_ZPSD_C03P"
575
, "KEY_ZPSD_C03T"
576
, "KEY_ZPSD_C03U"
577
, "KEY_ZPSD_C031"
578
, "KEY_ZPSD_C032"
579
, "KEY_ZPSD_C033"
580
, "KEY_ZPSD_C034"
581
, "/BIC/ZNET_ASP"
582
583
SELECT :i_pdimid_normal
584
, F."KEY_ZPSD_C03T"
585
, F."KEY_ZPSD_C03U"
586
, F."KEY_ZPSD_C031"
587
, F."KEY_ZPSD_C032"
588
, F."KEY_ZPSD_C033"
589
, F."KEY_ZPSD_C034"
590
, SUM( F."/BIC/ZNET_ASP" )
591
FROM "/BIC/FZPSD_C03" F
592
WHERE F."KEY_ZPSD_C03P" = :i_pdimid
Any thoughts would be helpful,
Thanks,
David

This error usually occurs when there is a database lock or no space in teh database. Got DB02 and Click on Space critical objects to see whether any entries are there. If yes contact your basis to increase the space.
Hope this helps
Thanks,
Satish

FDM Locations Lock Error in System 11

Similar Messages

Maybe you are looking for