AIX 5.3 ML3 에 9.2.0.6 patch 시 에러가 나네요..
error in writing to file
1. /oracle/lib/libvpxoafnd.so
2. /oracle/lib/libxdb.so
3. /oracle/lib/libwtc9.so
4. /oracle/lib/libvppdc.so
5. /oracle/lib/libjox9.a
6. /oracle/lib32/libclntsh.a
7. error in invoking target 'install' of makefile
/oracle/network/lib/ins_net_client.mk
8. /oracle/network/lib/ins_net_server.mk
9.2.0.6 패치시 에러뜰때 무시하면서 넘어가니 총 위와같은 에러들이 뜨는데..
os 버전과 9.2.0.6 사이에 호환문제 등이 있는지..
도움말 주실수 있으시면 부탁합니다.
정확한 패치를 하셨는지요?
패치버젼이 AIX 5L이 맞는지요?
우선 정확하게 download를 했는지 봐야겠지요.
Errors In Linking During Oracle 9.2 Installation On AIX 5L
note 406559.1
를 보면..
CauseUsing the wrong software for installation. The error "discontinued XCOFF64 file" clearly indicates that the software used is for AIX 4.3. Solution1. Download the installation software for Aix 5L based system and install the binaries. You can download the software from OTN site.
For AIX 5L the software to download for 9.2 is "Oracle9i Database Release 2 Enterprise/Standard Edition for AIX- Based 5L Systems"
2. Remove the binaries of the failed oracle installation from the Oracle Home.
3. Install the software using the newly downloaded installation software.
Similar Messages
-
Solved -Oracle 10.2.0.1 on AIX 5.3 ML3 - Error in invoking target 'ntcontab
Hello,
i try to Upgrade from oracle 9.2.0.7 to Oracle 10.2.0.1.
But the Linking to not work.
The Paket: bos-adm-libm is installt.
The Oracle Installer say - all OK, no errors.
The Script: rootpre.sh i run as user: root, befor i strart runInstaller
Here is a part of the file: /oracle/SAP1/oraInventory/logs/installActions2008-05-16_03-23-23PM.log
INFO: Start output from spawned process:
INFO: ----------------------------------
INFO:
INFO: rm -f ntcontab.*
INFO: (if [ "assemble" = "compile" ] ; then /oracle/SAP1/1020_64/bin/gennttab > ntcontab.c ; /oracle/SAP1/1020_64/bin/oraxlc -c ntcontab.c ; rm -f /oracle/SAP1/1020_64/lib/ntcontab.o ; mv ntcontab.o /oracle/SAP1/1020_64/lib/ ; /bin/ar -
X64 rv /oracle/SAP1/1020_64/lib/libn10.a /oracle/SAP1/1020_64/lib/ntcontab.o ; fi)
INFO: (if [ "assemble" = "assemble" ] ; then /oracle/SAP1/1020_64/bin/gennttab > ntcontab.s ; /bin/as -a64 -o ntcontab.o ntcontab.s ; rm -f /oracle/SAP1/1020_64/lib/ntcontab.o ; mv ntcontab.o /oracle/SAP1/1020_64/lib/ ; /bin/ar -X64 rv
/oracle/SAP1/1020_64/lib/libn10.a /oracle/SAP1/1020_64/lib/ntcontab.o ; fi)
INFO: Assembler:
INFO: ntcontab.s: line 20: 1252-023 The symbol t1 is not defined.
ntcontab.s: line 20: 1252-040 The specified expression is not valid.
Make sure that all symbols are defined.
Check the rules on symbols used in an arithmetic expression
concerning relocation.
INFO: make: 1254-004 The error code from the last command is 1.
Stop.
INFO: End output from spawned process.
INFO: ----------------------------------
INFO: Exception thrown from action: make
Exception Name: MakefileException
Exception String: Error in invoking target 'ntcontab.o' of makefile '/oracle/SAP1/1020_64/network/lib/ins_net_client.mk'. See '/oracle/SAP1/oraInventory/logs/installActions2008-05-16_03-23-23PM.log' for details.
Exception Severity: 1
make -f ins_net_client.mk install
/bin/chmod 755 /oracle/SAP1/920_64/bin/
- Linking
rm -f trcroute
ld -b64 -o trcroute -L/oracle/SAP1/920_64/network/lib/ -L/oracle/SAP1/920_64/lib/ /oracle/SAP1/920_64/network/lib/s0nur.o /oracle/SAP1/920_64/network/lib/nur.o `cat /oracle/SAP1/920_64/lib/ldflags` -lnsslb9 -lncrypt9 -lnsgr9 -lnzjs9 -ln9 -lnl9 -lnro9 `cat /oracle/SAP1/920_64/lib/ldflags` -lnsslb9 -lncrypt9 -lnsgr9 -lnzjs9 -ln9 -lnl9 -lclient9 -lvsn9 -lwtc9 -lcommon9 -lgeneric9 -lwtc9 -lmm -lnls9 -lcore9 -lnls9 -lcore9 -lnls9 -lxml9 -lcore9 -lunls9 -lnls9 `cat /oracle/SAP1/920_64/lib/ldflags` -lnsslb9 -lncrypt9 -lnsgr9 -lnzjs9 -ln9 -lnl9 -lnro9 `cat /oracle/SAP1/920_64/lib/ldflags` -lnsslb9 -lncrypt9 -lnsgr9 -lnzjs9 -ln9 -lnl9 -lclient9 -lvsn9 -lwtc9 -lcommon9 -lgeneric9 -lpls9 -ltrace9 -lnls9 -lcore9 -lnls9 -lcore9 -lnls9 -lxml9 -lcore9 -lunls9 -lnls9 -lclient9 -lvsn9 -lwtc9 -lcommon9 -lgeneric9 -lnls9 -lcore9 -lnls9 -lcore9 -lnls9 -lxml9 -lcore9 -lunls9 -lnls9 -lld -lm `cat /oracle/SAP1/920_64/lib/sysliblist` -lm `if [ "\`/usr/bin/uname -v\`" = "4" ]; \
then echo "-bI:/oracle/SAP1/920_64/lib/pw-syscall.exp"; fi;` -lxsd9 /oracle/SAP1/920_64/lib/nautab.o /oracle/SAP1/920_64/lib/naeet.o /oracle/SAP1/920_64/lib/naect.o /oracle/SAP1/920_64/lib/naedhs.o /oracle/SAP1/920_64/rdbms/lib/defopt.o -lmm
mv -f /oracle/SAP1/920_64/bin/trcroute /oracle/SAP1/920_64/bin/trcroute0
mv trcroute /oracle/SAP1/920_64/bin/trcroute
/bin/chmod 751 /oracle/SAP1/920_64/bin/trcroute
make: 1254-002 Cannot find a rule to create target ionrsd from dependencies.
Stop.
But the ENV: LIBRARY_PATH=/oracle/SAP1/920_64
i have delete with export LIBRARY_PATH=
before i run the runInstaller
If i set the ORACLE_HOME and LIBRARY_PATH
the i can see this:
make -f ins_net_client.mk install
/bin/chmod 755 /oracle/SAP1/1020_64/bin/
- Linking trcroute
rm -f trcroute
ld -b64 -o trcroute -L/oracle/SAP1/1020_64/network/lib/ -L/oracle/SAP1/1020_64/lib/ /oracle/SAP1/1020_64/network/lib/s0nur.o /oracle/SAP1/1020_64/network/lib/nur.o `cat /oracle/SAP1/1020_64/lib/ldflags` -lnsslb10 -lncrypt10 -lnsgr
10 -lnzjs10 -ln10 -lnnz10 -lnl10 -lnro10 `cat /oracle/SAP1/1020_64/lib/ldflags` -lnsslb10 -lncrypt10 -lnsgr10 -lnzjs10 -ln10 -lnnz10 -lnl10 -lclieSAP10 -lnnetd10 -lvsn10 -lcommon10 -lgeneric10 -lmm -lsnls10 -lnls10 -lcore10 -lsnls10
-lnls10 -lcore10 -lsnls10 -lnls10 -lxml10 -lcore10 -lunls10 -lsnls10 -lnls10 -lcore10 -lnls10 `cat /oracle/SAP1/1020_64/lib/ldflags` -lnsslb10 -lncrypt10 -lnsgr10 -lnzjs10 -ln10 -lnnz10 -lnl10 -lnro10 `cat /oracle/SAP1/1020_64/lib/ldf
lags` -lnsslb10 -lncrypt10 -lnsgr10 -lnzjs10 -ln10 -lnnz10 -lnl10 -lclieSAP10 -lnnetd10 -lvsn10 -lcommon10 -lgeneric10 -lpls10 -lsnls10 -lnls10 -lcore10 -lsnls10 -lnls10 -lcore10 -lsnls10 -lnls10 -lxml10 -lcore10 -lunls10 -lsnls
10 -lnls10 -lcore10 -lnls10 -lclieSAP10 -lnnetd10 -lvsn10 -lcommon10 -lgeneric10 -lsnls10 -lnls10 -lcore10 -lsnls10 -lnls10 -lcore10 -lsnls10 -lnls10 -lxml10 -lcore10 -lunls10 -lsnls10 -lnls10 -lcore10 -lnls10 -lld -lm `cat /oracle
/SAP1/1020_64/lib/sysliblist` -lm `if [ "\`/usr/bin/uname -v\`" = "4" ]; \
then echo "-bI:/oracle/SAP1/1020_64/lib/pw-syscall.exp"; fi;` /oracle/SAP1/1020_64/lib/nautab.o /oracle/SAP1/1020_64/lib/naeet.o /oracle/SAP1/1020_64/lib/naect.o /oracle/SAP1/1020_64/lib/naedhs.o /oracle/SAP1/1020_64/rdbms/lib/defopt.
o -lmm
mv -f /oracle/SAP1/1020_64/bin/trcroute /oracle/SAP1/1020_64/bin/trcroute0
mv trcroute /oracle/SAP1/1020_64/bin/trcroute
/bin/chmod 751 /oracle/SAP1/1020_64/bin/trcroute
- Linking
rm -f tnsping
ld -b64 -o tnsping -L/oracle/SAP1/1020_64/network/lib/ -L/oracle/SAP1/1020_64/lib/ /oracle/SAP1/1020_64/network/lib/s0nsping.o /oracle/SAP1/1020_64/network/lib/nsping.o `cat /oracle/SAP1/1020_64/lib/ldflags` -lnsslb10 -lncrypt10 -
lnsgr10 -lnzjs10 -ln10 -lnnz10 -lnl10 -lnro10 `cat /oracle/SAP1/1020_64/lib/ldflags` -lnsslb10 -lncrypt10 -lnsgr10 -lnzjs10 -ln10 -lnnz10 -lnl10 -lclieSAP10 -lnnetd10 -lvsn10 -lcommon10 -lgeneric10 -lmm -lsnls10 -lnls10 -lcore10 -lsn
ls10 -lnls10 -lcore10 -lsnls10 -lnls10 -lxml10 -lcore10 -lunls10 -lsnls10 -lnls10 -lcore10 -lnls10 `cat /oracle/SAP1/1020_64/lib/ldflags` -lnsslb10 -lncrypt10 -lnsgr10 -lnzjs10 -ln10 -lnnz10 -lnl10 -lnro10 `cat /oracle/SAP1/1020_64/li
b/ldflags` -lnsslb10 -lncrypt10 -lnsgr10 -lnzjs10 -ln10 -lnnz10 -lnl10 -lclieSAP10 -lnnetd10 -lvsn10 -lcommon10 -lgeneric10 -lpls10 -lsnls10 -lnls10 -lcore10 -lsnls10 -lnls10 -lcore10 -lsnls10 -lnls10 -lxml10 -lcore10 -lunls10 -
lsnls10 -lnls10 -lcore10 -lnls10 -lclieSAP10 -lnnetd10 -lvsn10 -lcommon10 -lgeneric10 -lsnls10 -lnls10 -lcore10 -lsnls10 -lnls10 -lcore10 -lsnls10 -lnls10 -lxml10 -lcore10 -lunls10 -lsnls10 -lnls10 -lcore10 -lnls10 -lld -lm `cat /o
racle/SAP1/1020_64/lib/sysliblist` -lm `if [ "\`/usr/bin/uname -v\`" = "4" ]; \
then echo "-bI:/oracle/SAP1/1020_64/lib/pw-syscall.exp"; fi;` /oracle/SAP1/1020_64/lib/nautab.o /oracle/SAP1/1020_64/lib/naeet.o /oracle/SAP1/1020_64/lib/naect.o /oracle/SAP1/1020_64/lib/naedhs.o /oracle/SAP1/1020_64/rdbms/lib/defopt.
o -lmm
mv -f /oracle/SAP1/1020_64/bin/tnsping /oracle/SAP1/1020_64/bin/tnsping0
mv tnsping /oracle/SAP1/1020_64/bin/tnsping
/bin/chmod 751 /oracle/SAP1/1020_64/bin/tnsping
Target "install" is up to date.
What did i wrong ?
The AIX is fresh bootet, without any oracle process start at boottime
Thanks and have a nice weekend
Dennis
Message was edited by:
user636686
Message was edited by:
user636686
Message was edited by:
user636686
Message was edited by:
user636686
Message was edited by:
user636686here are my env from the user i run the runInstaller:
STAGING_AREA=/oracle/stage/920_64
ORACLE_PSRV=SAP1
PATH=/oracle/SAP1/1020_64/bin:/usr/sap/NT1/SYS/exe/run:/bin:/usr/bin:/usr/sbin:/usr/bin/X11:/usr/ucb:/usr/ccs/b
in:/usr/local/bin:/etc:.
SAPBACKUP=/oracle/SAP1/sapbackup
ORACLE_BASE=/oracle
HISTFILE=/oracle/SAP1/.sh_history
TMP=/oracle/SAP1
SAPTRACE=/oracle/SAP1/saptrace
LIBARY_PATH=/oracle/SAP1/1020_64
ORACLE_SID=SAP1
SAPDATA_HOME=/oracle/SAP1
HOME=/oracle/SAP1
SAPARCH=/oracle/SAP1/saparch
ORACLE_HOME=/oracle/SAP1/1020_64
PWD=/oracle/dvd/Disk0/database/Disk1
ENV=/oracle/SAP1/.kshrc
SAPREORG=/oracle/SAP1/sapreorg
xlC.aix50.rte 9.0.0.5 COMMITTED XL C/C++ Runtime for AIX 5.2
xlC.rte 9.0.0.5 COMMITTED XL C/C++ Runtime
xlC.cpp 6.0.0.0 COMMITTED C for AIX Preprocessor
xlC.msg.en_US.cpp 6.0.0.0 COMMITTED C for AIX Preprocessor
gcc-4.2.0-3 -
MDM installation on AIX 5.3 core dumps
Hi all,
We installed MDM 5.5 SP4 on AIX 5.3 ML 5 (and the latest patches were applied last week-end).
The MDM Server, Import and Syndication daemons are started.
Database is Oracle 10.2 (corresponding Oracle client is used), installed on the same server.
MDM client software is in sync with the server level.
Since the installation, we get core dumps of the mds daemon (even when trying to perform the most basic operations). Consider it to be completely unusable for testing anything. You look at it, it breaks. Sorry, but that is how it is.
MDM Patches and hotfixes to the patches have been applied up to the latest level The problem is reported at SAP Support and they have core dumps, logfiles, trace files for studying. So far, the only feedback we got was to install MDM on its own server (it is a trial installation on a server where other applications are running - though I can hardly see that as a cause for core dumps).
My questions :
- are we unique in running MDM on this software paltform ?
- are others (if they exist experiencing the same problems on AIX 5.3 ?
To be honest : for the moment we are thinking about reinstalling on a Windows server.
Thanks in advance for any feedback,
Frank Van OverloopHello,
we have finally made some progress on this issue.
Basically, we suffered from a combination of :
- wrong usage of the product
- probably shaky exception handling in the AIX version
The cause was found by SAP MDM support after we reconstructed the problem while using a special debug-version of the mds executable. This produced a usable dump.
--- extract from the SAP reply -
The core dump shows a crash in recalculating the family tree after the
import. Family tree is being used only to create printed catalogs (which require the publisher and an additional license).
1) Do you have any value in the categories table?
2) Does the MDM server crash if you cancel the automatic family tree
recalculation in the import map, and answer "no" in the dialog box which asks to recalculate the family tree?
3) Do you intend to create a printed catalog?
If the answer to any of the questions is "no", then this asserts that
the recalculation of the family tree should not take place at all. In
this case the family table could/should be deleted. And this should not
reoccur.
end extract -
After we deleted this family table, the tests are running stable.
It's a pity that the program does not 'die' in a more elegant way or gives some understandable indication on what is going wrong.
It also looks like this exception is handled better on the Windows implementation. The same 'functional mistake' was made there and this produced no dumps at all. Could be a porting issue from one platform to another.
Regards,
Frank -
Database migration/upgrade from Linux (10.2.0.3) to AIX (10.2.0.5)
We are migrating 120+ Oracle 10gR2 databases (10.2.0.1, 10.2.0.3 & 10.2.0.5) from 30+ physical Linux (RHEL 4.6 & 5) servers to an AIX 6.1 virtualized environment running on two new P770 servers. Our migration approach will be to use Datapump Export and Import as we are moving between platforms and 95% of the databases are 5-10 Gb in size, so long export/import times should not be an issue. We have access to IBM's Xenobridge migration tool, but will try to do most of the work manually to offset the tool's high license cost.
Our server team is in the process of creating our AIX image(s) and we are preparing for the Oracle software installation . My question relates to the Oracle 10gR2 patch level on the new target AIX servers as our client has asked about patching all migrated databases up to 10.2.0.5.
Can I simply install the 10.2.0.1 base software on the AIX server, apply patch 10.2.0.5 and follow-up patch p10248542 before importing?
Is my upgrade approach then to simply export the 10.2.0.1 or 10.2.0.3 databases on Linux using the lower version of the Export utility and import into a copy on the AIX server using the 10.2.0.5 Import utility?
Will the Import utility take care of the upgrade from 10.2.0.1 or 10.2.0.3 to the 10.2.0.5 level?
Do I have to perform a manual upgrade and should there be any outstanding issues specifically related to Daylight Savings Time operability?
Here's my high level plan:
1. Install 10gR2 on AIX server and patch to 10.2.0.5
2. Export 10.2.0.3 database on Linux server using 10.2.0.3 Export utility
3. Use DBCA on Linux server to create "database create" template and transfer this template to AIX server for later use
4. Create "shell" database on AIX using DBCA on AIX server referencing template copied over from the Linux server
5. Import 10.2.0.3 database export into 10.2.0.5 shell database
Just wondering if all the steps in the 10.2.0.5 patchset notes (Readme for 8202632) still apply when using the export/import approach?
All feedback and comments around missing steps would be greatly appreciated.
Thank you,
JeffYour approach is correct - imp/exp (or impdp/expdp) will work. You can ignore the notes in 8202632. I would highly recommend that you perform a test upgrade first to validate, tweak as needed, and perfect your process.
See http://download.oracle.com/docs/cd/B19306_01/server.102/b14238/expimp.htm#i262220
Pl also review MOS Doc (Migration of Oracle Database Instances Across OS Platforms)
HTH
Srini -
오라클 SUN-64bit (8174-64bit) - AIX 5.3-64bit (8174-32bit)로 이행시 확인/문제점
Sun Solaris 5.8-64bit (Oracle 8174-64bit)를
IBM AIX 5.3-64bit (Oracle 8174-32bit with patch 2896876)로 exp/imp를 이용하여 이행하려 합니다.
(AIX 5L에 8174는 8174-32bit(with patch 2896876)밖에는 설치할 수 없습니다. )
이렇게 64bit->32bit로 AP단과 DB단 이행시 확인 및 문제점이 있다면 조언 부탁드립니다.
감사합니다.exp/imp는 word size에 대한 제한을 가지지 않습니다.
OS와 상관없이 논리적인 데이터를 가지고 오기 때문이지요. -
SAPSQL_ARRAY_INSERT_DUPREC during saving of Process Chain
Dear all,
On saving, when adding a process to an existing Process Chain - like Rollup or Change Run - in our SCM 5.0 system, we receive a short dump 'SAPSQL_ARRAY_INSERT_DUPREC' (complete short dump at the end of the msg).
A problem arose on the line 'insert rsbatchparallel from table g_t_batch_par.' of include 'LRSBATCHF01'.
The version of this include is the same as all other systems in our environment.
In the table 'rsbatchparallel' we don't find any entry that can cause a duplicate entry.
We are really stuck with this issue - any help is highly appreciated!
Best regards,
Ingrid
Complete short dump
Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC
Exception CX_SY_OPEN_SQL_DB
Date and Time 08.10.2007 16:56:50
Short text
The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLRSBATCH" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
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.
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 caught
in
procedure "SAVE_SETTINGS" "(FORM)", nor was it propagated by a RAISING 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:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
How to correct the error
Use an ABAP/4 Open SQL array insert only if you are sure that none of
the records passed already exists in the database.
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:
"SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"
"SAPLRSBATCH" or "LRSBATCHF01"
"SAVE_SETTINGS"
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.
The exception must either be prevented, caught within proedure
"SAVE_SETTINGS" "(FORM)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "eccdb603"
Network address...... "19.106.69.177"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "00C485BD4C00"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "eccdb603"
Database type..... "DB6"
Database name..... "A8P"
Database user ID.. "SAPA8P"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Mar 19 2007 20:40:49"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "DB6_81 "
Patch level. 102
Patch text.. " "
Database............. "DB6 08.02., DB6 09."
SAP database version. 700
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory consumption
Roll.... 16192
EM...... 25139088
Heap.... 0
Page.... 212992
MM Used. 16132952
MM Free. 4812888
User and Transaction
Client.............. 510
User................ "IERNAELS"
Language key........ "E"
Transaction......... "RSPC "
Transactions ID..... " "
Program............. "SAPLRSBATCH"
Screen.............. "SAPLRSSM_PROCESS 0100"
Screen line......... 19
Information on where terminated
Termination occurred in the ABAP program "SAPLRSBATCH" - in "SAVE_SETTINGS".
The main program was "RSPC_MAINTAIN ".
In the source code you have the termination point in line 1082
of the (Include) program "LRSBATCHF01".
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "SAVE_SETTINGS" "(FORM)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "SAPLRSBATCH "; its source code begins in line
1045 of the (Include program "LRSBATCHF01 ".
Source Code Extract
Line
SourceCde
1052
loop at g_t_batch_par.
1053
if g_t_batch_par-pc_variant is initial.
1054
l_var = '//SPACE//SPACE//SPACE//SPACE//'.
1055
else.
1056
l_var = g_t_batch_par-pc_variant.
1057
endif.
1058
do.
1059
call function 'ENQUEUE_ERSBATCHSERVER'
1060
exporting
1061
mode_rsbatchserver = 'E'
1062
process_type = g_t_batch_par-process_type
1063
pc_variant = l_var
1064
_scope = '3'
1065
_wait = 'X'
1066
exceptions
1067
foreign_lock = 1.
1068
if sy-subrc = 0.
1069
exit.
1070
endif.
1071
enddo.
1072
endloop.
1073
1074
loop at g_t_batch_par.
1075
delete from rsbatchparallel where
1076
process_type = g_t_batch_par-process_type and
1077
pc_variant = g_t_batch_par-pc_variant.
1078
delete from rsbatchserver where
1079
process_type = g_t_batch_par-process_type and
1080
pc_variant = g_t_batch_par-pc_variant.
1081
endloop.
>>>>>
insert rsbatchparallel from table g_t_batch_par.
1083
insert rsbatchserver from table g_t_batch_serv.
1084
call function 'DB_COMMIT'.
1085
1086
loop at g_t_batch_par.
1087
if g_t_batch_par-pc_variant is initial.
1088
l_var = '//SPACE//SPACE//SPACE//SPACE//'.
1089
else.
1090
l_var = g_t_batch_par-pc_variant.
1091
endif.
1092
do.
1093
call function 'DEQUEUE_ERSBATCHSERVER'
1094
exporting
1095
mode_rsbatchserver = 'E'
1096
process_type = g_t_batch_par-process_type
1097
pc_variant = l_var
1098
_scope = '3'
1099
_synchron = 'X'.
1100
if sy-subrc = 0.
1101
exit.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
3
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
0001
SY-UCOMM
SAVE
SY-TITLE
Process Maintenance: Attribute Change Run
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
1
SY-DATUM
20071008
SY-UZEIT
165610
SY-XPROG
SAPFGUICNTL
SY-XFORM
%_CONTROL_EXIT_DYNPRO
Active Calls/Events
No. Ty. Program Include Line
Name
20 FORM SAPLRSBATCH LRSBATCHF01 1082
SAVE_SETTINGS
19 FUNCTION SAPLRSBATCH LRSBATCHU08 279
RSBATCH_MAINTAIN_PAR_SETTINGS
18 FORM SAPLRSSM_PROCESS LRSSM_PROCESSF04 1917
MAINTAIN_PARALLEL_SETTINGS
17 MODULE (PAI) SAPLRSSM_PROCESS LRSSM_PROCESSI01 125
USER_COMMAND_0100
16 FUNCTION SAPLRSPC_VARIANT LRSPC_VARIANTU01 93
RSPC_VARIANT_MAINTAIN
15 FUNCTION SAPLRSSM_PROCESS LRSSM_PROCESSU01 56
RSSM_PROCESS_VARIANT_DIALOG
14 METHOD CL_RSSM_ATTRIBCHANGE==========CP CL_RSSM_ATTRIBCHANGE==========CM003 3
CL_RSSM_ATTRIBCHANGE=>IF_RSPC_MAINTAIN~MAINTAIN
13 METHOD CL_RSPC_FRONTEND==============CP CL_RSPC_FRONTEND==============CM00E 16
CL_RSPC_FRONTEND=>_EDIT_NODE
12 METHOD CL_RSPC_FRONTEND==============CP CL_RSPC_FRONTEND==============CM00T 139
CL_RSPC_FRONTEND=>_ON_MENU_SEL
11 METHOD CL_RSPC_FRONTEND==============CP CL_RSPC_FRONTEND==============CM016 40
CL_RSPC_FRONTEND=>_ON_NET_DOUBLECLICK
10 METHOD CL_GUI_RSNETGRAPHIC_NETPLAN===CP CL_GUI_RSNETGRAPHIC_NETPLAN===CM00W 40
CL_GUI_RSNETGRAPHIC_NETPLAN=>_HANDLE_OBJECTDBLCLICK
9 METHOD CL_GUI_RSNETGRAPHIC_NETPLAN===CP CL_GUI_RSNETGRAPHIC_NETPLAN===CM005 37
CL_GUI_RSNETGRAPHIC_NETPLAN=>HANDLE_EVENTS
8 METHOD CL_GUI_RSNETGRAPHIC_NETPLAN===CP CL_GUI_RSNETGRAPHIC_NETPLAN===CM003 3
CL_GUI_RSNETGRAPHIC_NETPLAN=>DISPATCH
7 METHOD CL_GUI_CFW====================CP CL_GUI_CFW====================CM00K 173
CL_GUI_CFW=>DISPATCH_SYSTEM_EVENTS
6 FORM SAPFGUICNTL_CFW SAPFGUICNTL_CFW 23
CONTROL_DISPATCH
5 FORM SAPFGUICNTL SAPFGUICNTL 20
CONTROL_DISPATCH
4 FORM SAPMSSYD SAPMSSYD 288
%_CTL_INPUT
3 MODULE (PAI) SAPMSSYD SAPMSSYD 236
%_CTL_INPUT1
2 FUNCTION SAPLRSPC_FRONTEND LRSPC_FRONTENDU10 76
RSPC_CHAIN_MAINTAIN
1 EVENT RSPC_MAINTAIN RSPC_MAINTAIN 11
START-OF-SELECTION
Chosen variables
Name
Val.
No. 20 Ty. FORM
Name SAVE_SETTINGS
G_T_400_SAVE
Table[initial]
<%_TABLE_RSBATCHSERVER>
SYST-REPID
SAPLRSBATCH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454554454422222222222222222222222222222
310C232143800000000000000000000000000000
G_H_DEBUG_TYPE
Table[initial]
SY-REPID
SAPLRSBATCH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454554454422222222222222222222222222222
310C232143800000000000000000000000000000
G_T_WAIT
0.1.
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222220022222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
G_T_BATCH_PAR-PROCESS_TYPE
ATTRIBCHAN
0000000000
0000000000
4555444444
144292381E
%_DUMMY$$
0000
0000
2222
0000
G_T_300_OBJECT[]
Table[initial]
G_T_BATCH_PAR-PC_VARIANT
CHANGE_RUN_MASTER_DATA
000000000000000000000000000000
000000000000000000000000000000
444444555454455455445422222222
381E75F25EFD13452F414100000000
G_T_300_OBJECT
0000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222223333
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
<%_TABLE_RSBATCHPARALLEL>
G_S_ADM-PRIORITY
0
0
2
0
G_T_BATCH_PAR[]
Table IT_8429[3x212]
FUNCTION-POOL=RSBATCHDATA=G_T_BATCH_PAR[]
Table reference: 176
TABH+ 0(20) = 0700000040337FA0000000000000000000000000
TABH+ 20(20) = 000000B0000020ED00000003000000D4FFFFFFFF
TABH+ 40(16) = 04000276000007400010249401800000
store = 0x0700000040337FA0
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 176 (0x000000B0)
label = 8429 (0x000020ED)
fill = 3 (0x00000003)
leng = 212 (0x000000D4)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000024
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x07000000410D8D60
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 6428 (0x0000191C)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x00000010)
lineAlloc = 16 (0x00000010)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x00000001)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
G_T_BATCH_SERV[]
Table IT_8430[2x166]
FUNCTION-POOL=RSBATCHDATA=G_T_BATCH_SERV[]
Table reference: 181
TABH+ 0(20) = 07000000410D9AB8000000000000000000000000
TABH+ 20(20) = 000000B5000020EE00000002000000A6FFFFFFFF
TABH+ 40(16) = 04000276000003E00010249401800000
store = 0x07000000410D9AB8
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 181 (0x000000B5)
label = 8430 (0x000020EE)
fill = 2 (0x00000002)
leng = 166 (0x000000A6)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000006
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x0700000040360F08
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 6429 (0x0000191D)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x00000010)
lineAlloc = 16 (0x00000010)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x00000001)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
No. 19 Ty. FUNCTION
Name RSBATCH_MAINTAIN_PAR_SETTINGS
I_NO_DIALOG
0
0
2
0
I_TYPE
ATTRIBCHAN
0000000000
0000000000
4555444444
144292381E
I_VARIANT
CHANGE_RUN_MASTER_DATA
000000000000000000000000000000
000000000000000000000000000000
444444555454455455445422222222
381E75F25EFD13452F414100000000
E_T_SERVER
Table[initial]
C_T_BATCH_PAR[]
Table IT_8427[3x210]
FUNCTION-POOL=RSSM_PROCESSFORM=MAINTAIN_PARALLEL_SETTINGSDATA=L_T_PAR
Table reference: 377
TABH+ 0(20) = 070000004050EFA8070000004033896000000000
TABH+ 20(20) = 00000179000020EB00000003000000D2FFFFFFFF
TABH+ 40(16) = 040001900000CEF00010249401800000
store = 0x070000004050EFA8
ext1 = 0x0700000040338960
shmId = 0 (0x00000000)
id = 377 (0x00000179)
label = 8427 (0x000020EB)
fill = 3 (0x00000003)
leng = 210 (0x000000D2)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#001089
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x0700000040332390
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 6426 (0x0000191A)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x00000010)
lineAlloc = 16 (0x00000010)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x00000001)
>>>>> 1st level extension part <<<<<
regHook = 0x0000000000000000
collHook = 0x0000000000000000
ext2 = 0x070000004110CD08
>>>>> 2nd level extension part <<<<<
tabhBack = 0x0700000040F34148
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x0000000000000000
pb_handle = 0x0000000000000000
G_T_CLASS_100[]
Table IT_8436[3x122]
FUNCTION-POOL=RSBATCHDATA=G_T_CLASS_100[]
Table reference: 355
TABH+ 0(20) = 07000000410F9E48070000004110865000000000
TABH+ 20(20) = 00000163000020F4000000030000007AFFFFFFFF
TABH+ 40(16) = 0400027600000B900010249401800000
store = 0x07000000410F9E48
ext1 = 0x0700000041108650
shmId = 0 (0x00000000)
id = 355 (0x00000163)
label = 8436 (0x000020F4)
fill = 3 (0x00000003)
leng = 122 (0x0000007A)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000047
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x070000004081DE00
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 6435 (0x00001923)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x00000010)
lineAlloc = 16 (0x00000010)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x00000001)
>>>>> 1st level extension part <<<<<
regHook = 0x0000000000000000
collHook = 0x0000000000000000
ext2 = 0x07000000406795C8
>>>>> 2nd level extension part <<<<<
tabhBack = 0x07000000410FB438
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x0000000000000000
pb_handle = 0x0000000000000000
G_T_CLASS_100
C'C'
0000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000
4242222222222222222222222222222222222222222222222222222222222
3737000000000000000000000000000000000000000000000000000000000
%_FL2*CTRL_SERVER
1
0000
0001
G_T_CLASS_100-TEXT
'C'
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
242222222222222222222222222222222222222222222222222222222222
737000000000000000000000000000000000000000000000000000000000
TEXT-008
'C'
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
24222222222222222222222222222222222222222222222222
73700000000000000000000000000000000000000000000000
SAVEOK
SAVE
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
5454222222222222222222222222222222222222222222222222222222222222222222
3165000000000000000000000000000000000000000000000000000000000000000000
OKCODE
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000
G_SUBRC
0
0000
0000
G_FIRST_TIME_100
0
0
2
0
G_T_WP_400
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
G_500_WP_NO
000
000
222
000
CX_TRUE
X
0
0
5
8
SY-MSGID
00000000000000000000
00000000000000000000
22222222222222222222
00000000000000000000
SPACE
0
0
2
0
SY-MSGNO
000
000
000
333
000
SY-MSGV1
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV2
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV3
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SY-MSGV4
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
No. 18 Ty. FORM
Name MAINTAIN_PARALLEL_SETTINGS
SY-REPID
SAPLRSSM_PROCESS
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454555455544455222222222222222222222222
310C233DF02F3533000000000000000000000000
SYST-REPID
SAPLRSSM_PROCESS
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454555455544455222222222222222222222222
310C233DF02F3533000000000000000000000000
P_VARIANT
CHANGE_RUN_MASTER_DATA
000000000000000000000000000000
000000000000000000000000000000
444444555454455455445422222222
381E75F25EFD13452F414100000000
G_T_BATCH_PAR
ATTRIBCHANCHANGE_RUN_MASTER_DATA 03C
000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000
455544444444444455545445545544542222222233422
144292381E381E75F25EFD13452F41410000000003300
G_T_BATCH_PAR[]
Table IT_8382[3x90]
FUNCTION-POOL=RSSM_PROCESSDATA=G_T_BATCH_PAR[]
Table reference: 344
TABH+ 0(20) = 070000004049B188000000000000000000000000
TABH+ 20(20) = 00000158000020BE000000030000005AFFFFFFFF
TABH+ 40(16) = 04000190000016A00010249401800000
store = 0x070000004049B188
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 344 (0x00000158)
label = 8382 (0x000020BE)
fill = 3 (0x00000003)
leng = 90 (0x0000005A)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000106
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x0700000040F33B90
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 6392 (0x000018F8)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x00000010)
lineAlloc = 16 (0x00000010)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x00000001)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
L_PC_TYPE
ATTRIBCHAN
0000000000
0000000000
4555444444
144292381E
SPACE
0
0
2
0
P_PC_TYPE
ATTRIBCHAN
0000000000
0000000000
4555444444
144292381E
L_T_PAR
Table IT_8427[3x210]
L_S_PAR
ATTRIBCHANCHANGE_RUN_MASTER_DATA 03C
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
4555444444444444555454455455445422222222334222222222222222222222222222222222222222222222222222
144292381E381E75F25EFD13452F414100000000033000000000000000000000000000000000000000000000000000
G_S_CHAIN
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
G_T_F4
Table IT_4031[5x222]
FUNCTION-POOL=RSSM_PROCESSDATA=G_T_F4
Table reference: 122
TABH+ 0(20) = 0700000040293BE0000000000000000000000000
TABH+ 20(20) = 0000007A00000FBF00000005000000DEFFFFFFFF
TABH+ 40(16) = 04000190000009B00010249401800000
store = 0x0700000040293BE0
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 122 (0x0000007A)
label = 4031 (0x00000FBF)
fill = 5 (0x00000005)
leng = 222 (0x000000DE)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000037
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x070000004035B278
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 3652 (0x00000E44)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x00000010)
lineAlloc = 16 (0x00000010)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x00000001)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>&When modifying the PC, you are likely using a process variant twice, or, using a variant already used somewhere else.
-
We have a problem when execute the next steps in GRC Access Control 10.0
SPRO-->Governance, Risk and Compliance>Access Control--> Access Risk Analysis--> Batch RisK Analysis
We applied the next note, but problem is the same.
1563583 - SYSTEM_NO_TASK_STORAGE dump on AIX
Category
ABAP Programming Error
Runtime Errors
ASSERTION_FAILED
ABAP Program
CL_GRRM_DASHBOARD_MENU_AUTH===CP
Application Component GRC-RM
Date and Time
13.03.2013 11:50:04
|Short text
|
|
The ASSERT condition was violated.
|
|What happened?
|
|
In the running application program, the ASSERT statement recognized a
|
|
situation that should not have occurred.
|
|
The runtime error was triggered for one of these reasons:
|
|
- For the checkpoint group specified with the ASSERT statement, the
|
|
activation mode is set to "abort".
|
|
- Via a system variant, the activation mode is globally set to "abort"
|
|
for checkpoint groups in this system.
|
|
- The activation mode is set to "abort" on program level.
|
|
- The ASSERT statement is not assigned to any checkpoint group.
|
|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.
|
|Error analysis
|
|
The following checkpoint group was used: "No checkpoint group specified"
|
|
|
|
If in the ASSERT statement the addition FIELDS was used, you can find
|
|
the content of the first 8 specified fields in the following overview:
|
|
" (not used) "
|
|
" (not used) "
|
|
" (not used) "
|
|
" (not used) "
|
|
" (not used) "
|
|
" (not used) "
|
|
" (not used) "
|
|
" (not used) "
|
|How to correct the error
|
|
Probably the only way to eliminate the error is to correct the program.
|
|
|
|
|
|
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:
|
|
|
|
"ASSERTION_FAILED" " "
|
|
"CL_GRRM_DASHBOARD_MENU_AUTH===CP" or "CL_GRRM_DASHBOARD_MENU_AUTH===CM001"
|
|
"IF_GRFN_MENU_ITEM_AUTH~IS_AUTHORIZED"
|
|
|
|
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..... 702
|
|
SAP Basis Level. 0012
|
|
|
|
Application server... "KIO13701"
|
|
Network address...... "172.20.1.137"
|
|
Operating system..... "AIX"
|
|
Release.............. "7.1"
|
|
Hardware type........ "00F6C78E4C00"
|
|
Character length.... 16 Bits
|
|
Pointer length....... 64 Bits
|
|
Work process number.. 10
|
|
Shortdump setting.... "full"
|
|
|
|
Database server... "KIO13701"
|
|
Database type..... "DB6"
|
|
Database name..... "DGR"
|
|
Database user ID.. "SAPDGR"
|
|
|
|
Terminal.......... "192.168.0.5"
|
|
|
|
Char.set.... "C"
|
|
|
|
SAP kernel....... 720
|
|
created (date)... "Jul 8 2012 19:43:01"
|
|
create on........ "AIX 2 5 00092901D600"
|
|
Database version. "DB6_81 "
|
|
|
|
Patch level. 300
|
|
Patch text.. " "
|
|
|
|
Database............. "DB6 08.02.*, DB6 09.*, DB6 10.*"
|
|
SAP database version. 720
|
|
Operating system..... "AIX 2 5, AIX 3 5, AIX 1 6, AIX 1 7"
|
|
|
|
Memory consumption
|
|
Roll.... 0
|
|
EM...... 8379584
|
|
Heap.... 0
|
|
Page.... 16384
|
|
MM Used. 6205712
|
|
MM Free. 2170976
|
|User and Transaction
|
|
Client.............. 100
|
|
User................ "LVELASCO"
|
|
Language key........ "E"
|
|
Transaction......... " "
|
|
Transaction ID...... "51400164B1F00C40E1008000AC140189"
|
|
|
|
EPP Whole Context ID.... "5140015EB1F00C40E1008000AC140189"
|
|
EPP Connection ID....... "5140F9B0B19C1150E1008000AC140189"
|
|
EPP Caller Counter...... 1
|
|
|
|
Program............. "CL_GRRM_DASHBOARD_MENU_AUTH===CP"
|
|
Screen.............. "SAPMHTTP 0010"
|
|
Screen Line......... 2
|
|
Debugger Active..... "none"
|
|Server-Side Connection Information
|
|
Information on Caller of "HTTPS" Connection:
|
|
Plug-in Type.......... "HTTPS"
|
|
Caller IP............. "192.168.0.5"
|
|
Caller Port........... 44300
|
|
Universal Resource ID. "/sap/bc/webdynpro/sap/grfn_service_map"
|
|
|
|
Program............. "CL_GRRM_DASHBOARD_MENU_AUTH===CP"
|
|
Screen.............. "SAPMHTTP 0010"
|
|
Screen Line......... 2
|
|
|
|
Information on Caller ofr "HTTPS" Connection:
|
|
Plug-in Type.......... "HTTPS"
|
|
Caller IP............. "192.168.0.5"
|
|
Caller Port........... 44300
|
|
Universal Resource Id. "/sap/bc/webdynpro/sap/grfn_service_map"
|
|Information on where terminated
|
|
Termination occurred in the ABAP program "CL_GRRM_DASHBOARD_MENU_AUTH===CP" -
|
|
in "IF_GRFN_MENU_ITEM_AUTH~IS_AUTHORIZED".
|
|
The main program was "SAPMHTTP ".
|
|
|
|
In the source code you have the termination point in line 59
|
|
of the (Include) program "CL_GRRM_DASHBOARD_MENU_AUTH===CM001".
|
|Source Code Extract (Source code has changed)
|
|Line |SourceCde
|
| 29|
lv_dashboard = lv_value.
|
| 30|
|
| 31|
TRANSLATE lv_dashboard TO UPPER CASE.
|
| 32|
|
| 33|
CASE lv_dashboard.
|
| 34|
WHEN 'HEATMAP'.
|
| 35|
lv_report = 'GRRM_HEATMAP'.
|
| 36|
|
| 37|
WHEN 'LOSS_OVERVIEW' OR 'LOSS_STRUCTURE' OR 'OB_LOSS_OVERVIEW' OR 'OB_LOSS_STRUCTU|
| 38|
lv_report = 'GRRM_LOSS_ANALYSIS'.
|
| 39|
|
| 40|
WHEN 'OVERVIEW'.
|
| 41|
lv_report = 'GRRM_OVERVIEW'.
|
| 42|
|
| 43|
WHEN OTHERS.
|
| 44|
ASSERT 1 = 2.
|
| 45|
|
| 46|
ENDCASE.
|
| 47|
|
| 48|
EXIT.
|
| 49|
|
| 50|
ENDLOOP.
|
| 51|
|
| 52|
WHEN 'GRRM_LOSS_MATRIX' OR 'GRRM_LOSS_MATRIX_NEW'.
|
| 53|
lv_report = 'GRRM_LOSS_ANALYSIS'.
|
| 54|
|
| 55|
WHEN 'GRRM_HEATMAP_REPORT'.
|
| 56|
lv_report = 'GRRM_HEATMAP'.
|
| 57|
|
| 58|
WHEN OTHERS.
|
|>>>>>|
ASSERT 1 = 2.
|
| 60|
|
| 61| ENDCASE.
|
| 62|
|
| 63| TRY.
|
| 64|
lv_regulation_id = cl_grfn_api_regulation=>if_grfn_api_regulation~get_regulation_id( i|
| 65|
|
| 66|
ev_authorized = cl_grfn_util_rep_auth=>has_rep_auth(
|
| 67|
io_session
= io_session
|
| 68|
iv_regulation_id = lv_regulation_id
|
| 69|
iv_report
= lv_report
|
| 70|
iv_activity
= grfn0_c_activity-print
|
| 71|
|
| 72|
|
| 73|
CATCH cx_grfn_exception.
|
| 74|
ev_authorized = abap_false.
|
| 75|
|
| 76| ENDTRY.
|
| 77|
|
| 78|ENDMETHOD.
|
|Contents of system fields
|
|Name
|Val.
|
|SY-SUBRC|4
|
|SY-INDEX|2
|
|SY-TABIX|1
|
|SY-DBCNT|1
|
|SY-FDPOS|0
|
|SY-LSIND|0
|
|SY-PAGNO|0
|
|SY-LINNO|1
|
|SY-COLNO|1
|
|SY-PFKEY|
|
|SY-UCOMM|
|
|SY-TITLE|HTTP Control
|
|SY-MSGTY|
|
|SY-MSGID|
|
|SY-MSGNO|000
|
|SY-MSGV1|
|
|SY-MSGV2|
|
|SY-MSGV3|
|
|SY-MSGV4|
|
|SY-MODNO|0
|
|SY-DATUM|20130313
|
|SY-UZEIT|115004
|
|SY-XPROG|SAPCNVE
|
|SY-XFORM|CONVERSION_EXIT
|
|Active Calls/Events
|
|No. Ty.
Program
Include
Line |
|
Name
|
| 34 METHOD
CL_GRRM_DASHBOARD_MENU_AUTH===CP
CL_GRRM_DASHBOARD_MENU_AUTH===CM001
59 |
|
CL_GRRM_DASHBOARD_MENU_AUTH=>IF_GRFN_MENU_ITEM_AUTH~IS_AUTHORIZED
|
| 33 METHOD
CL_GRFN_API_MENU_ITEM_ELA=====CP
CL_GRFN_API_MENU_ITEM_ELA=====CM001 126 |
|
CL_GRFN_API_MENU_ITEM_ELA=>IF_GRFN_MENU_AUTH~ITEM_AUTH
|
| 32 METHOD
CL_GRFN_API_MENU==============CP
CL_GRFN_API_MENU==============CM003
34 |
|
CL_GRFN_API_MENU=>IF_GRFN_MENU_AUTH~ITEM_AUTH
|
| 31 METHOD
CL_GRFN_LAUNCHPAD_UIBB========CP
CL_GRFN_LAUNCHPAD_UIBB========CM006
60 |
|
CL_GRFN_LAUNCHPAD_UIBB=>IF_FPM_GUIBB_LAUNCHPAD~MODIFY
|
| 30 METHOD
CL_FPM_LAUNCHPAD_UIBB_ASSIST==CP
CL_FPM_LAUNCHPAD_UIBB_ASSIST==CM001
76 |
|
CL_FPM_LAUNCHPAD_UIBB_ASSIST=>INIT_FEEDER
|
| 29 METHOD
/1BCWDY/T2POSMRSKMLY9L6LJP5Z==CP
/1BCWDY/B_T2POSBAR6C8HPR0XTR4P
410 |
|
CL_COMPONENTCONTROLLER_CTR=>WDDOINIT
|
|
Web Dynpro Component
FPM_LAUNCHPAD_UIBB
|
|
Controller
COMPONENTCONTROLLER
|
| 28 METHOD
/1BCWDY/T2POSMRSKMLY9L6LJP5Z==CP
/1BCWDY/B_T2POSBAR6C8HPR0XTR4P
181 |
|
CLF_COMPONENTCONTROLLER_CTR=>IF_WDR_COMPONENT_DELEGATE~WD_DO_INIT
|
|
Web Dynpro Component
FPM_LAUNCHPAD_UIBB
|
|
Controller
COMPONENTCONTROLLER
|
| 27 METHOD
CL_WDR_DELEGATING_COMPONENT===CP
CL_WDR_DELEGATING_COMPONENT===CM004
9 |
|
CL_WDR_DELEGATING_COMPONENT=>DO_INIT
|
| 26 METHOD
CL_WDR_CONTROLLER=============CP
CL_WDR_CONTROLLER=============CM00V
3 |
|
CL_WDR_CONTROLLER=>INIT_CONTROLLER
|
| 25 METHOD
CL_WDR_COMPONENT==============CP
CL_WDR_COMPONENT==============CM019
24 |
|
CL_WDR_COMPONENT=>INIT_CONTROLLER
|
| 24 METHOD
CL_WDR_CONTROLLER=============CP
CL_WDR_CONTROLLER=============CM002
7 |
|
CL_WDR_CONTROLLER=>INIT
|
| 23 METHOD
CL_WDR_CLIENT_COMPONENT=======CP
CL_WDR_CLIENT_COMPONENT=======CM00E
24 |
|
CL_WDR_CLIENT_COMPONENT=>INIT
|
| 22 METHOD
CL_WDR_CLIENT_COMPONENT=======CP
CL_WDR_CLIENT_COMPONENT=======CM00A
42 |
|
CL_WDR_CLIENT_COMPONENT=>IF_WDR_COMPONENT_FACTORY~CREATE_COMPONENT
|
| 21 METHOD
CL_WDR_COMPONENT_USAGE========CP
CL_WDR_COMPONENT_USAGE========CM009
67 |
|
CL_WDR_COMPONENT_USAGE=>IF_WD_COMPONENT_USAGE~CREATE_COMPONENT
|
| 20 METHOD
CL_FPM_COMPONENT_MANAGER======CP
CL_FPM_COMPONENT_MANAGER======CM003
81 |
|
CL_FPM_COMPONENT_MANAGER=>ADD_COMPONENT
|
| 19 METHOD
CL_FPM_COMPONENT_MANAGER======CP
CL_FPM_COMPONENT_MANAGER======CM004
19 |
|
CL_FPM_COMPONENT_MANAGER=>ATTACH_COMPONENT_TO_USAGE
|
| 18 METHOD
CL_FPM========================CP
CL_FPM========================CM005
89 |
|
CL_FPM=>PROCESS_EVENT
|
| 17 METHOD
CL_FPM========================CP
CL_FPM========================CM00C
34 |
|
CL_FPM=>RUN_EVENT_LOOP
|
| 16 METHOD
CL_FPM========================CP
CL_FPM========================CM002
5 |
|
CL_FPM=>IF_FPM~RAISE_EVENT
|
| 15 METHOD
CL_FPM========================CP
CL_FPM========================CM003
11 |
|Hi Alberto,
The below Notes should resolve!
1428775
1744179
Hope this helps,
Luciana -
Short Dump while INSERTING to a DB Z table
There is one report that we are running in production. Earlier it was taking about 2hrs to run and now it's taking about 14-15 hours to run after we applied the Support Pack. I must agree that the report is not well written by the previous developers and I have been asked to rewrite it but in the meanwhile, they want to continue running the old one.
This report deletes all the existing records first and then updates a Z table. Last week when they tried to run the report as batch job it got cancelled after running 22000 secounds and my basis team told me that logs are getting saturated and we need to use Truncate Statement instead of DELETE from table statement and that is what I did but again when they tried running the report in production it got cancelled again and this time after 55000 secs and this time it's getting cancelled in the last step when we are inserting the records back to the table from the internal table.
So can you please tell me how can I take care of this.
My Findings:
1. Report updates a Z table for 700K records which is really not a very big size.
2. Z table size category is customized for upto 48K to 93K . Does this matter when I try to update 700K records at a time.
3. There is no foreign key relations in the Z table
4. I feel that, it could be a basis problem like, memory related. Any light on this?
5. The program currently uses INSERT statement.Can I try for a success using MODIFY statement. All validations are handled before inserting to remove the duplicates.So I dont see any issues using INSERT statement
6. Can we use a commit statement after INSERT or MODIFY?
7. From SAP help, I see that there is a limitation on the number of records can be inserted or modified. Any idea on the number?
Thanks & Best Regards,
Kiran Babu DasariDump:
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Date and Time 01/01/2009 10:17:22
Short text
SQL error in the database when accessing a table.
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.
How to correct the error
Database error text........: "SQL0964C The transaction log for the database is
full. SQLSTATE=57011 row=1"
Internal call code.........: "[RSQL/INSR/ZTMM_PU_FOR_BW ]"
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_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
"ZPMM_BWLOAD_R_V2" or "ZPMM_BWLOAD_INC02"
"FILL_ZTMM_PU_FOR_BW"
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.
The exception must either be prevented, caught within proedure
"FILL_ZTMM_PU_FOR_BW" "(FORM)", or its possible occurrence must be declared in
the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "ucerp13"
Network address...... "192.168.254.23"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "00C4B5BE4C00"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 34
Shortdump setting.... "full"
Database server... "ucerp10"
Database type..... "DB6"
Database name..... "RP1"
Database user ID.. "SAPRP1"
Terminal................. " "
Char.set.... "C"
SAP kernel....... 700
created (date)... "Oct 26 2008 20:51:39"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "DB6_81 "
Patch level. 183
Patch text.. " "
Database............. "DB6 08.02., DB6 09."
SAP database version. 700
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
Memory consumption
Roll.... 16192
EM...... 234631488
Heap.... 0
Page.... 24576
MM Used. 28706288
MM Free. 197532304
User and Transaction
Client.............. 400
User................ "BATCHUC"
Language key........ "E"
Transaction......... " "
Transactions ID..... "49597E9619C40076E1008000C0A8FE17"
Program............. "ZPMM_BWLOAD_R_V2"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "ZPMM_BWLOAD_R_V2" - in
"FILL_ZTMM_PU_FOR_BW".
The main program was "ZPMM_BWLOAD_R_V2 ".
In the source code you have the termination point in line 2886
of the (Include) program "ZPMM_BWLOAD_INC02".
The program "ZPMM_BWLOAD_R_V2" was started as a background job.
Job Name....... "ZPMM_BWLOAD_R_V2"
Job Initiator.. "BATCHSCHED"
Job Number..... 10261500
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "FILL_ZTMM_PU_FOR_BW" "(FORM)", but it was neither handled locally
nor declared
in the RAISING clause of its signature.
The procedure is in program "ZPMM_BWLOAD_R_V2 "; its source code begins in line
2751 of the (Include program "ZPMM_BWLOAD_INC02 ".
Source Code Extract
Line
SourceCde
2856
itab_result-rec_no = recnum.
2857
ENDIF.
2858
2859
11/30/05 - Change it back after sorting
2860
IF linetype = 'AAA'.
2861
itab_result-linetype = 'INI'.
2862
ENDIF.
2863
itab_result-extractdate = e_sdate.
2864
itab_result-mandant = sy-mandt.
2865
MODIFY itab_result INDEX indx.
2866
2867
SELECT SINGLE
2868
rec_no
2869
ponumber
2870
FROM ztmm_pu_for_bw
2871
INTO CORRESPONDING FIELDS OF itab_duprec
2872
WHERE rec_no = recnum
2873
AND ponumber = pono
2874
AND linetype = linetype
2875
AND line_no = lineno
2876
AND changenr = chgno
2877
AND chgind_h = indh
2878
AND chgind_p = indp
2879
AND tblname = tbl
2880
AND fldname = fld.
2881
IF sy-subrc <> 0.
2882
MOVE-CORRESPONDING itab_result TO itab_result_bw.
2883
APPEND itab_result_bw.
2884
nrecs_results = nrecs_results + 1.
2885
>>>>>
INSERT ztmm_pu_for_bw FROM TABLE itab_result_bw.
2887
INSERT zztmm_pu_for_bw FROM TABLE itab_result_bw.
2888
2889
CLEAR itab_result_bw.
2890
REFRESH itab_result_bw.
2891
ENDIF.
2892
ENDLOOP.
2893
*change to array insert for performance
2894
INSERT ZZTMM_PU_FOR_BW FROM TABLE itab_result_bw.
2895
2896
ENDFORM. " fill_ztmm_pu_for_bw
Contents of system fields
Name
Val.
SY-SUBRC
4
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Load Purchasing Info. for BW Reporting
SY-MSGTY
E
SY-MSGID
TD
SY-MSGNO
600
SY-MSGV1
T710-08L04
SY-MSGV2
K01
SY-MSGV3
EN
SY-MSGV4
SY-MODNO
0
SY-DATUM
20081231
SY-UZEIT
190013
SY-XPROG
SAPCNVE
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No. Ty. Program Include Line
Name
2 FORM ZPMM_BWLOAD_R_V2 ZPMM_BWLOAD_INC02 2886
FILL_ZTMM_PU_FOR_BW
1 EVENT ZPMM_BWLOAD_R_V2 ZPMM_BWLOAD_R_V2 192
START-OF-SELECTION
Chosen variables
Name
Val.
No. 2 Ty. FORM
Name FILL_ZTMM_PU_FOR_BW
SY
#######ৡ###################A###P#################ż#############################T#######린 u#̀##
00000000000000000000000000000000000000010000000000000000000000000000000000000000000000FB000000
000000090000000000000000000000000000000A0000000001000000000000000000000000000000000000F9000300
0000000E0000000000000000000400050000000B0000000007000000000000000000000000000105000000FB270000
0000010100000000000000000101010000000000000000040C000000000000000000000000000604000000F005000C
ITAB_RESULT_BW-WAERS
USD
00000
00000
55422
53400
ITAB_RESULT-WAERS
USD
00000
00000
55422
53400
ITAB_RESULT_BW+5358(10)
#U#C# #
0205040202
0005030000
ITAB_RESULT+4160(10)
#U#C# #
0205040202
0005030000
AMTCRCHGPOSREGUA2
00000000000
0000000000C
ITAB_RESULT_BW+5378(572)
#S#h#i#p#p#i#n#g# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
0205060607070606060202020202020202020202020202020202020202020202020202020202020202020202020202
000308090000090E070000000000000000000000000000000000000000000000000000000000000000000000000000
ITAB_RESULT+4170(572)
#S#h#i#p#p#i#n#g# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
0205060607070606060202020202020202020202020202020202020202020202020202020202020202020202020202
000308090000090E070000000000000000000000000000000000000000000000000000000000000000000000000000
C_INITIAL
@0E@
000000
000000
434422
005000
ITAB_RESULT_BW-ORT01
Cincinnati
00000000000000000000000000000000000
00000000000000000000000000000000000
46666666762222222222222222222222222
39E39EE1490000000000000000000000000
ITAB_RESULT-ORT01
Cincinnati
00000000000000000000000000000000000
00000000000000000000000000000000000
46666666762222222222222222222222222
39E39EE1490000000000000000000000000
ITAB_RESULT_BW-PSTLZ
45206
0000000000
0000000000
3333322222
4520600000
ITAB_RESULT-PSTLZ
45206
0000000000
0000000000
3333322222
4520600000
ITAB_RESULT_BW-REGIO
OH
000
000
442
F80
ITAB_RESULT-REGIO
OH
000
000
442
F80
ITAB_RESULT_BW-STRAS
2709 Woodburn Ave.
00000000000000000000000000000000000
00000000000000000000000000000000000
33332566667762476222222222222222222
270907FF4252E0165E00000000000000000
ITAB_RESULT-STRAS
2709 Woodburn Ave.
00000000000000000000000000000000000
00000000000000000000000000000000000
33332566667762476222222222222222222
270907FF4252E0165E00000000000000000
%_SPACE
0
0
2
0
ITAB_RESULT_BW+6154(4)
0202
0000
ITAB_RESULT+4908(4)
0202
0000
LW_LINES
164
000A
0004
ITAB_RESULT_BW-TELF1
961-1122
0000000000000000
0000000000000000
3332333322222222
961D112200000000
ITAB_RESULT-TELF1
961-1122
0000000000000000
0000000000000000
3332333322222222
961D112200000000
ITAB_RESULT_BW-LAND1
US
000
000
552
530
ITAB_RESULT-LAND1
US
000
000
552
530
COUNTROCHGNEGCONOVER1K2
0
0000
0000
ITAB_RESULT_BW+6158(337)
#0#3#6#0#-#0#0# # # # # # # # # # # # # #M#R#O# #&# #C#o#n#s#t#r#u#c#t#i#o#n#A#t#h#l#e#t#i#c
0203030303020303020202020202020202020202020405040202020406060707070706070606060407060606070606
00000306000D0000000000000000000000000000000D020F000600030F0E030402050304090F0E0104080C05040903
ITAB_RESULT+4950(337)
#0#3#6#0#-#0#0# # # # # # # # # # # # # #M#R#O# #&# #C#o#n#s#t#r#u#c#t#i#o#n#A#t#h#l#e#t#i#c
0203030303020303020202020202020202020202020405040202020406060707070706070606060407060606070606
00000306000D0000000000000000000000000000000D020F000600030F0E030402050304090F0E0104080C05040903
ITAB_CHGLOG[]
Table IT_33[587x1576]
\PROGRAM=ZPMM_BWLOAD_R_V2\DATA=ITAB_CHGLOG[]
Table reference: 25
TABH+ 0(20) = 070000009070DB38000000000000000000000000
TABH+ 20(20) = 00000019000000210000024B00000628FFFFFFFF
TABH+ 40(16) = 040000000000149000082C9401800000
store = 0x070000009070DB38
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 25 (0x00000019)
label = 33 (0x00000021)
fill = 587 (0x0000024B)
leng = 1576 (0x00000628)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000095
occu = 8 (0x00000008)
access = 1 (ItAccessStandard)
idxKind = 1 (ItIndexLinear)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x07000000A0E13E70
pgHook = 0x07000000B2EBC728
idxPtr = 0x07000000906BA5E0
shmTabhSet = 0x0000000000000000
id = 32 (0x00000020)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 1024 (0x00000400)
lineAlloc = 592 (0x00000250)
shmVersId = 0 (0x00000000)
shmRefCount = 469 (0x000001D5)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
ITAB_RESULT_BW+3592(1026)
0202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ITAB_RESULT+5798(1026)
0202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ITAB_RESULT_BW-MANDANT
400
000
000
333
400
ITAB_RESULT-MANDANT
400
000
000
333
400
AMTTCCHGPOSREGST2
00000000000
0000000000C
ITAB_RESULT_BW[]
Table IT_132[1x6760]
\PROGRAM=ZPMM_BWLOAD_R_V2\DATA=ITAB_RESULT_BW[]
Table reference: 51
TABH+ 0(20) = 07000000A9A1FEA8000000000000000000000000
TABH+ 20(20) = 00000033000000840000000100001A68FFFFFFFF
TABH+ 40(16) = 0400000000003140000224C401800000
store = 0x07000000A9A1FEA8
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 51 (0x00000033)
label = 132 (0x00000084)
fill = 1 (0x00000001)
leng = 6760 (0x00001A68)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000248
occu = 2 (0x00000002)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x07000000A283E980
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 141 (0x0000008D)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 2 (0x00000002)
lineAlloc = 2 (0x00000002)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x00000001)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
ITAB_RESULT_BW
400##͒4500034945
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000030000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3330053333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
4000024500034945000000000000000000000000000000000000000000000000000000000000000000000000000000
%_DUMMY$$
0000
0000
2222
0000
COUNTTCCHGNEGCONST3
0
0000
0000
<%_TABLE_ZTMM_PU_FOR_BW>
AMTTOTAL3
00000000000
0000000000C
No. 1 Ty. EVENT
Name START-OF-SELECTION
T023T
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
T024
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
T161
00000 00000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222223333322222222222222222222222222222222222333332222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
TWLAD
000000000000000000000000
000000000000000000000000
222222222222222222222222
000000000000000000000000
ZTMM_BOA
0000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222223333333333333333222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ZTMM_PU_FOR_BW
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2220002222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ZTPU_DOCTYPE
0000000000000000000000000000000000
0000000000000000000000000000000000
2222222222222222222222222222222222
0000000000000000000000000000000000
USR02
####0000000000000000 # 000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222220000333333333333333322222222222220222222222222222222222222333333333333333333333
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SSCRFIELDS
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
C_BLUESQUAREX
@3X@
000000
000000
435422
038000
Internal notes
The termination was triggered in function "HandleRsqlErrors"
of the SAP kernel, in line 786 of the module
"//bas/700_REL/src/krn/runt/absapsql.c#11".
The internal operation just processed is "SQLS".
Internal mode was started at 20081231190002.
Internal call code.........: "[RSQL/INSR/ZTMM_PU_FOR_BW ]"
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit = unlimited
=> Stack limit = 4294967296
=> Core limit = 1073741312
=> File size limit = unlimited
=> Heap address = 0x0x11c0f5d60
=> Stack address = 0xfffffffffff8040
=> Stack low = 0xfffffffffff8040
=> Stack high = 0xffffffffffff800
=> Stack Trace:
AixStack() at 0x1000c945c
CTrcStack2() at 0x1000c9554
rabax_CStackSave__Fv() at 0x1000b3ee0
ab_rabax() at 0x1000b0628
ab_rsqlerr__FPCUsiT1P11RS_HEADER94T1Pv() at 0x10058c010
HandleRsqlErrors__F9RsqlError9CloseMode() at 0x1017f1e94
SqlsExecuteCall__FUcP11DynCallInfo() at 0x1017efc68
ab_jsqls__Fv() at 0x1017ea82c
ab_extri__Fv() at 0x100419ca0
ab_xevent__FPCUs() at 0x10094e47c
ab_trigg__Fv() at 0x10094e168
ab_run() at 0x1011aabb8
N_ab_run() at 0x100f6edc0
dynpmcal() at 0x100f6d9c4
dynppai0() at 0x100f6b2c8
dynprctl() at 0x100f7375c
dynpen00() at 0x100f6761c
Thdynpen00() at 0x1000e3c6c
TskhLoop() at 0x1000e5b64
ThStart() at 0x1001000c0
DpMain() at 0x101301d34
nlsui_main() at 0x101abea68
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
ZPMM_BWLOAD_R_V2
0
12/31/2008
10:10:08
409600
E
1
Prg
SAPMSSY0
1
05/30/2008
12:59:05
92160
E
2
Prg
SAPMSSYD
1
08/16/2006
12:06:37
21504
E
3
Prg
SAPFSYSCALLS
1
09/09/2004
14:18:32
7168
E
4
Prg
RSDBRUNT
0
12/13/2008
02:15:03
254976
E
5
Prg
SAPLSPRI
5
12/13/2008
02:14:06
342016
E
6
Typ
PRI_PARAMS
0
11/02/1998
09:46:12
5120
7
Typ
ARC_PARAMS
0
08/28/1997
08:36:28
6144
8
Typ
PRI_LAYOUT
0
11/06/2003
20:30:04
2048
9
Typ
PRIPAR_EXT
0
05/18/2004
14:07:03
3072
10
Typ
PRIPAR_EX2
0
11/09/2000
14:10:39
2048
11
Typ
PRIPAR_EX3
0
05/18/2004
14:07:03
5120
12
Typ
TPRI_DEF
0
11/09/2000
14:24:28
5120
13
Typ
USR01
0
05/30/2008
19:06:47
4096
14
Typ
TSP1D
0
11/15/2000
17:58:02
5120
15
Prg
SAPLSPOO
15
12/13/2008
02:14:06
160768
E
16
Prg
SAPLRSPOLSTDRV
16
12/13/2008
02:13:54
58368
E
17
Typ
TSPOPTIONS
0
01/29/1997
19:13:56
2048
18
Typ
TSP03
0
11/02/1998
09:57:05
5120
19
Typ
TSP0A
0
11/15/2000
17:58:02
6144
20
Typ
TSP03C
0
11/21/2003
11:41:10
7168
21
Typ
TSP03T
0
03/23/1998
18:21:38
6144
22
Typ
TSP06A
0
11/15/2000
17:58:02
7168
23
Prg
SAPCNVE
23
09/09/2004
14:36:10
8192
E
24
Prg
SAPLSPOC
24
12/13/2008
02:15:07
137216
E
25
Typ
TSP03L
0
07/10/1997
00:46:18
2048
26
Typ
RSPOCHECK
0
08/13/1997
12:53:10
4096
27
Typ
TSP03A
0
07/10/1997
00:46:15
3072
28
Prg
SAPLSPOR
28
12/13/2008
02:15:07
39936
E
29
Prg
SAPLSPOB
29
05/30/2008
09:36:14
67584
E
30
Prg
SAPLSDEX
30
09/09/2004
14:20:42
22528
E
31
Typ
DD07T
0
05/30/2008
00:38:18
3072
32
Typ
DEVPAR
0
12/04/2000
12:46:11
3072
33
Typ
RSPOATTR
0
11/10/1999
17:44:19
2048
34
Typ
RSSCR
0
03/30/2005
10:21:45
5120
35
Prg
RSDBSPBL
0
03/30/2005
10:21:58
72704
E
36
Prg
SAPDB__S
0
03/30/2005
10:22:01
19456
E
37
Typ
VARID
0
05/12/1997
16:51:30
4096
38
Typ
SSCRFIELDS
0
05/13/1997
12:54:26
5120
39
Prg
%_CSYDB0
0
03/30/2005
10:21:45
35840
E
40
Prg
RSDBSPVA
0
12/13/2008
02:15:03
133120
E
41
Typ
RSVAMEMKEY
0
05/07/1997
13:07:49
5120
42
Prg
RSDBSPMC
0
08/16/2006
11:55:58
79872
E
43
Typ
DDSHDESCR
0
09/03/1997
03:05:16
4096
44
Typ
SPPARAMS
0
05/07/1997
13:10:38
2048
45
Prg
SAPLICON
45
05/30/2008
13:22:44
27648
E
46
Prg
%_CICON
45
05/30/2008
13:22:44
107520
E
47
Typ
ICONT
0
08/16/2006
11:55:57
2048
48
Prg
SAPLSABE
48
09/09/2004
14:18:36
12288
E
49
Prg
SAPLSECU
49
05/30/2008
11:07:13
87040
E
50
Typ
RSSUBINFO
0
10/14/1999
22:01:03
2048
51
Typ
RSEXFCODE
0
08/13/1997
12:52:57
2048
52
Prg
SAPLDSYA
52
05/30/2008
12:53:05
45056
E
53
Prg
SAPFSDS1
52
03/30/2005
10:22:01
52224
E
54
Typ
TDCLD
0
11/02/1998
09:51:35
6144
55
Prg
SAPLSDOD
55
01/25/2006
10:59:45
45056
E
56
Typ
DOKIL
0
05/12/1997
16:46:17
3072
57
Prg
SAPLLANG
57
09/09/2004
14:18:35
10240
E
58
Typ
T002
0
05/30/2008
00:53:58
2048
59
Prg
SAPFSPOR
0 -
Getting Dump at the time of opening WF
Hi,
we had created workflow WS93600011 in our development server. Till Friday 10.07.2009 it was working fine. We did some small change and activated the workflow. Till that time we were able to open the workflow template. On 13.06.2009 when we tried to open the workflow then it was giving dump, so accordingly we checked is this the problem with only 1 workflow template or all the workflow templates and we found that this is the problem with only 1 workflow template not all. So accordingly we did some analysis and I tried to check whether any SAP OSS Notes needs to be implemented but all the notes are already in place.
Please see below the what dump says...
Runtime Errors OBJECTS_OBJREF_NOT_ASSIGNED_NO
Except. CX_SY_REF_IS_INITIAL
Date and Time 07/20/2009 13:30:44
Short text
Access via 'NULL' object reference not possible.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_WFD_TASK_PROXY=============CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
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.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not caught in procedure "CONSTRUCTOR" "(METHOD)", nor was it propagated by a RAISING 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: You attempted to use a 'NULL' object reference (points to 'nothing') access a component. An object reference must point to an object (an instance of a class) before it can be used to access components. Either the reference was never set or it was set to 'NULL' using the CLEAR statement.
How to correct the error
Probably the only way to eliminate the error is to correct the program.
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:
"OBJECTS_OBJREF_NOT_ASSIGNED_NO" "CX_SY_REF_IS_INITIAL"
"CL_WFD_TASK_PROXY=============CP" or "CL_WFD_TASK_PROXY=============CM001"
"CONSTRUCTOR"
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.
The exception must either be prevented, caught within proedure
"CONSTRUCTOR" "(METHOD)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 701
Application server... "ydedb"
Network address...... "9.57.177.109"
Operating system..... "AIX"
Release.............. "6.1"
Hardware type........ "00C15EAF4C00"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 4
Shortdump setting.... "full"
Database server... "ydedb"
Database type..... "DB6"
Database name..... "YDE"
Database user ID.. "SAPYDE"
Terminal.......... "IBM-BE014934612"
Char.set.... "C"
SAP kernel....... 701
created (date)... "Mar 30 2009 21:48:51"
create on........ "AIX 2 5 00CB5A5B4C00"
Database version. "DB6_81 "
Patch level. 37
Patch text.. " "
Database............. "DB6 08.02.*, DB6 09.*"
SAP database version. 701
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
Memory consumption
Roll.... 16192
EM...... 8379696
Heap.... 0
Page.... 73728
MM Used. 3730104
MM Free. 457144
User and Transaction
Client.............. 210
User................ 013319744
Language key........ "E"
Transaction......... "PFTC "
Transactions ID..... "4A62BD9572AD004BE10080000939B16D"
Program............. "CL_WFD_TASK_PROXY=============CP"
Screen.............. "SAPLRHWS 1001"
Screen line......... 19
Information on where terminated
Termination occurred in the ABAP program "CL_WFD_TASK_PROXY=============CP" -
in "CONSTRUCTOR".
The main program was "SAPLRHW4 ".
In the source code you have the termination point in line 91
of the (Include) program "CL_WFD_TASK_PROXY=============CM001".
The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
procedure "CONSTRUCTOR" "(METHOD)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "CL_WFD_TASK_PROXY=============CP "; its source
code begins in line
1 of the (Include program "CL_WFD_TASK_PROXY=============CM001 ".
Source Code Extract
Line SourceCde
61 a_task = l_task.
62 ENDIF.
63 *-- load task
64 IF in_task IS NOT INITIAL.
65 a_task = in_task.
66 ENDIF.
67 CALL METHOD deserialize
68 EXPORTING
69 in_display = in_display
70 EXCEPTIONS
71 task_not_exists = 1
72 task_already_locked = 2
73 OTHERS = 3.
74 IF sy-subrc = 2.
75 *---- we couldn't lock in update mode -> create a proxy in display
76 *---- mode
77 CALL METHOD deserialize
78 EXPORTING
79 in_display = 'X'
80 EXCEPTIONS
81 task_not_exists = 1
82 task_already_locked = 2
83 OTHERS = 3.
84 ENDIF.
85 IF sy-subrc <> 0.
86 RAISE task_not_found.
87 ENDIF.
88 ENDIF.
89 * create before image on the container
90 TRY.
>>>>> CALL METHOD a_container->create_before_image
92 EXPORTING
93 include_extensions = 'X'.
94 CATCH cx_swf_cnt_container .
95 ENDTRY.
96
97 ENDMETHOD. "constructor
If any body is having any idea to resolve this issue then please let me know. We are into the last stage of the development.
Thanks in advance for replying this issue.
Best Regards,
Prashant RaichurkarHi Rick,
The small change I did into the business object and added those parameter into the task and workflow through binding. And you are right the changed I did was on 10/07 and I am getting dump from 13/07.
Also I already copied to copy the workflow template into another, in the new template everything is blank including workflow container and template. It is as like new template.
Also one thing I want to tell you that I thought to activate previous version so the moment I click on choose version again I got the same dump.
Please let me know if you have any idea to resolve this issue.
Thanks & Regards,
Prashant -
TYPELOAD_NEW_VERSION in SAP CRM 7.0
Hi,
Whenever we try to execute any workbench transaction like SE38 or SE37 and view any source code, we get the following runtime error:
Runtime Errors TYPELOAD_NEW_VERSION
Date and Time 09/10/2010 09:25:25
Short text
A newer version of data type "E071" was found than one required
What happened?
Runtime error
The current ABAP program "SAPLSEUQ" had to be terminated because one
of the statements could not be executed at runtime.
What can you do?
Restart the program.
If the error persists, 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
The data type "E071" was loaded from the database during the program run.
However, a type of a newer version than the one requried was found here.
How to correct the error
Try to restart the program.
System environment
SAP-Release 701
Network address...... "10.145.1.14"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "00CE94034C00"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database type..... "DB6"
Database name..... "CMS"
Database user ID.. "SAPR3A"
Terminal.......... "DTPXP-cmuriyad"
Char.set.... "C"
SAP kernel....... 701
created (date)... "Feb 3 2010 21:48:21"
create on........ "AIX 2 5 00CB5A5B4C00"
Database version. "DB6_81 "
Patch level. 79
Patch text.. " "
Database............. "DB6 08.02., DB6 09."
SAP database version. 701
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
Memory consumption
Roll.... 16192
EM...... 4189848
Heap.... 0
Page.... 24576
MM Used. 2920472
MM Free. 1266776
Information on where terminated
Termination occurred in the ABAP program "SAPLSEUQ" - in "DETERMINE_TADIR".
The main program was "RSABAPPROGRAM ".
In the source code you have the termination point in line 507
of the (Include) program "LSEUQF01".
Thanks,
Charles AntonyCharles,
I am not sure but go through SAP Notes 595104 - Runtime error TYPELOAD_NEW_VERSION & Note 480671 - The Text Language Flag of LANG Fields for pointers to the issue -
SAP ECC 6.0 System Performance
Gentlemen,
Please advise me with the following scenario, which is Iu2019m facing a problem with system performance,
My system configuration is: SAP ECC 6.0
Database System: Oracle 10.2.0.2.0.
Server Configuration: Power 6
Processor Type: PowerPC_POWER6
Processor Implementation Mode: POWER 6
Processor Version: PV_6_Compat
Number Of Processors: 6
Processor Clock Speed: 3503 MHz
CPU Type: 64-bit
Kernel Type: 64-bit
LPAR Info: 2 PRODUCTION
Memory Size: 47104 MB
Good Memory Size: 47104 MB
Platform Firmware level: EL340_039
Firmware Version: IBM,EL340_039
The following Information was generated from TCode: sm51:
SAP Release Information
Application Server SAPPRD_PRD_00
SAP Kernel Information
SAP Kernel : 700_REL
Database Client Library : OCI_101
created in : AIX 2 5 005DD9CD4C00
Support Level : 0
Kernel Patch number : 202
Source ID : 0.202
DBSL Patch No. : 046
ICU Version : 3.0 Unicode Version 4.0.1
libsapu16 Version : 1.0025 Apr 8 2009 16:21:08
Supported Environment
SAP Database Version
700
Database
ORACLE 9.2.0..
ORACLE 10.1.0..
ORACLE 10.2.0..
Operating System
aix 1 5
aix 2 5
aix 3 5
aix 1 6
My active parameter in Tcode : RZ10 as follow:
Parameter Name Parameter value
login/accept_sso2_ticket 1
login/create_sso2_ticket 2
rsau/enable 1
login/failed_user_auto_unlock 0
login/fails_to_user_lock 5
gw/max_sys 2000
gw/max_overflow_size 25000000
rdisp/max_comm_entries 2000
rdisp/tm_max_no 2000
gw/max_conn 2000
rdisp/max_arq 2000
ES/SHM_SEG_COUNT 8192
ES/SHM_USER_COUNT 8192
ES/SHM_SEG_SIZE 2048
ES/TABLE SHM_SEGS
ztta/short_area 4000000
em/global_area_MB 256
zcsa/db_max_buftab 10000
sap/bufdir_entries 10000
enque/table_size 60000
rsdb/obj/large_object_size 35000
rsdb/obj/max_objects 45000
rsdb/obj/buffersize 150000
rdisp/gui_auto_logout 0
login/password_expiration_time 0
rdisp/max_wprun_time 25000
login/multi_login_users CICUSER,TALSAYED,ASALAM
login/disable_multi_gui_login 1
SAPSYSTEMNAME PRD
SAPSYSTEM 0
INSTANCE_NAME DVEBMGS00
DIR_CT_RUN $(DIR_EXE_ROOT)/run
DIR_EXECUTABLE $(DIR_INSTANCE)/exe
PHYS_MEMSIZE 8000
exe/saposcol $(DIR_CT_RUN)/saposcol
rdisp/wp_no_dia 70
rdisp/wp_no_btc 20
exe/icmbnd $(DIR_CT_RUN)/icmbnd
icm/server_port_0 PROT=HTTP,PORT=80$$
ms/server_port_0 PROT=HTTP,PORT=81$$
rdisp/wp_no_enq 1
rdisp/wp_no_vb 2
rdisp/wp_no_vb2 2
rdisp/wp_no_spo 10
abap/buffersize 9900000
zcsa/table_buffer_area 108003328
rtbb/buffer_length 60000
rsdb/cua/buffersize 24000
zcsa/presentation_buffer_area 28166144
rdisp/appc_ca_blk_no 2000
rdisp/wp_ca_blk_no 1000
rsdb/ntab/entrycount 68500
rsdb/ntab/ftabsize 100000
rsdb/ntab/irbdsize 20000
rsdb/ntab/sntabsize 3995
DIR_ROLL /usr/sap/PRD/DVEBMGS00/data
DIR_PAGING /usr/sap/PRD/DVEBMGS00/data
DIR_DATA /usr/sap/PRD/DVEBMGS00/data
DIR_REORG /usr/sap/PRD/DVEBMGS00/data
DIR_TRANS /usr/sap/trans
DIR_TEMP /tmp
DIR_SORTTMP /usr/sap/PRD/DVEBMGS00/data
zcsa/system_language E
zcsa/installed_languages AE
abap/use_paging 0
ztta/roll_first 1024
rdisp/keepalive_timeout 8000
ztta/roll_area 9000960
rdisp/ROLL_SHM 16384
rdisp/ROLL_MAXFS 32768
rdisp/PG_SHM 16384
rdisp/PG_MAXFS 200064
abap/heap_area_dia 2012217344
abap/heap_area_nondia 2012217344
abap/heap_area_total 2012217344
abap/heaplimit 40894464
abap/swap_reserve 20971520
ztta/roll_extension 2101346304
em/initial_size_MB 4092
em/blocksize_KB 4096
em/stat_log_size_MB 20
em/stat_log_timeout 0
login/no_automatic_user_sapstar 0
login/system_client 100
icm/server_port_1 PROT=SMTP,PORT=8025,TIMEOUT=180
rdisp/start_icman TRUE
icm/host_name_full SAPPRD.tmg.dom
install/codepage/appl_server 4102
ipc/shm_psize_10 500000000
ipc/shm_psize_14 0
ipc/shm_psize_18 0
ipc/shm_psize_19 0
ipc/shm_psize_30 -10
ipc/shm_psize_40 500000000
ipc/shm_psize_41 0
ipc/shm_psize_51 -10
ipc/shm_psize_52 -10
ipc/shm_psize_54 -10
ipc/shm_psize_55 -10
ipc/shm_psize_57 -10
ipc/shm_psize_58 -10
I already generated EWA report and I got the following result:
1. Performance Overview PRD
The performance of your system was analyzed with respect to average response times and total workload. We have detected some problems that may impair system performance.
To ensure adequate performance in your core business transactions, you should take corrective action as soon as possible. For further information, please SAP Support.
Rating Check
Performance Evaluation
The following table shows the average response times for various task types:
Task type Dialog Steps Avg. Resp. Time in ms Avg. CPU Time in ms Avg. Wait Time in ms Avg. Load Time in ms Avg. DB Time in ms Avg. GUI Time in ms
DIALOG 212990 1595.2 257.7 31.0 5.0 622.2 136.8
RFC 2904 11876.4 192.1 33.1 1.4 10574.2 0.0
UPDATE 86257 116.1 28.4 2.1 2.9 58.1 0.0
UPDATE2 1100 84.6 16.9 1.3 1.4 48.2 0.0
BATCH 11600 189360.5 46218.1 5.5 3.7 132313.5 0.0
SPOOL 9989 1686.8 37.1 55.6 0.3 49.2 0.0
1.1. Current Workload
The following table lists the number of current users (measured from our workload analysis) in your system.
Users Low Activity Medium Activity High Activity Total Users
Measured in System 162 119 6 287
1.2. Performance Evaluation
The measured times are compared against reference times to provide a rating.
- If the number of dialog steps in an hour is less than 1000 this hour is not considered.
- If the total number of transaction steps is less than 24000, the rating for the task is not performed and a blue line is entered in the table.
The table below shows that a performance problem is expected for the task that is rated YELLOW.
Task Steps Application Server Performance Database Server Performance
Dia 212987
Upd 86257
HTTP 0
Rating Task Time Steps Avg. Response Time (ms) Avg. CPU Time (ms) Avg. Database Time (ms)
Dia 08-09 3726 1343 137 889
Dia 09-10 19990 1003 174 620
Dia 10-11 20603 1747 112 630
Dia 11-12 27934 2437 239 612
Dia 12-13 18921 2737 235 858
Dia 13-14 21579 2163 349 549
Dia 16-17 22529 1134 230 703
Dia 17-18 12189 1709 561 991
Dia 19-20 5840 1550 414 967
Dia 20-21 4951 1294 176 454
The ratings in the table above are determined by comparisons against the reference table below.
If the dialog response times are very poor, it will cause a RED rating for the entire check.
Task Reference for Avg. Response Time (ms) Reference for Avg. DB time (ms)
Dia 1200 600
Upd 2400 1200
HTTP 1200 600
1.3. Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the highest workload in your system. NOTE: A business transaction normally consists of more than one dialog step. As a rough estimate, the actual number of business transactions that are executed in your system is approximately one third of the total dialog steps shown. (Transaction CPIC/RFC is not taken into account.)
1.3.1. Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload.
WORKLOAD BY TRANSACTION (DIALOG/UPDATE)
Transaction Type Dialog Steps Total Resp. Time in % Avg. Resp. Time in ms Avg. CPU Time in ms Avg. DB Time in ms Avg. GUI Time in ms
Total 299247 100.0 1168.9 191.7 459.6 136.8
ZFIBB DIA 8592 11.1 4522.4 2258.5 633.4 30.1
ZFIRP DIA 6641 7.3 3858.0 1089.7 1162.6 50.0
RECN DIA 11644 6.8 2047.9 129.1 1165.8 202.6
SESSION_MANAGER DIA 8972 5.7 2226.9 80.2 244.2 458.2
ZFICCR DIA 4834 5.2 3775.9 138.4 2535.9 195.6
ZRECPD DIA 8895 4.6 1790.1 85.9 525.3 329.4
FBL3N DIA 10414 4.1 1386.7 109.3 971.8 49.1
ZFIOBC2 DIA 852 3.4 13909.2 2675.7 9302.3 1028.7
ZREOR DIA 2241 3.3 5216.1 2246.2 808.1 357.5
ZFIOB DIA 1176 3.2 9503.7 51.3 8287.0 753.4
38.1% of the "Total Resp. Time" in the above table is caused by customer transactions.
WORKLOAD BY TRANSACTION (BATCH/SPOOL)
Transaction Type Dialog Steps Total Resp. Time in % Avg. Resp. Time in ms Avg. CPU Time in ms Avg. DB Time in ms
Total 21492 100.0 102913.8 24939.7 71399.3
SBIE0001 BTC 36 98.7 60613763.4 14848709.4 42408448.0
ZFIPR SPO 448 0.2 7939.6 169.9 387.1
(BATCH) BTC 7368 0.2 478.4 7.5 22.2
ZFIADCA SPO 486 0.1 5733.7 168.6 177.9
RSAL_BATCH_TOOL_DISPATCHING BTC 96 0.1 23895.0 1964.7 21770.3
ZFIJV SPO 309 0.1 6092.5 107.7 89.5
SAPRSLOG BTC 4 0.1 318475.8 69165.0 257824.5
ZRE_GENERATE_COND_RO BTC 5 0.1 250075.0 3336.0 237287.8
ZRE_AUTO_REJECT_OFFER BTC 20 0.1 57062.0 339.0 54977.8
ZRE_TRANSFER_TOCONT_UPL BTC 346 0.0 3161.3 941.6 2327.7
0.6% of the "Total Resp. Time" in the above table is caused by customer transactions.
According to our analysis, the main system load is caused by background jobs.
The EarlyWatch Alert Service can only detect performance problems for dialog, update and RFC response times. This service does not evaluate performance problems for background jobs.
1.3.2. Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load, sorted by percentage of total database access times.
DATABASE LOAD BY TRANSACTIONS (DIALOG/UPDATE)
Transaction Type Dialog Steps Total DB Time in % Avg. DB Time in ms
Total 299247 100.0 459.6
RECN DIA 11644 9.9 1165.8
ZFICCR DIA 4834 8.9 2535.9
FBL3N DIA 10414 7.4 971.8
ZFIOB DIA 1176 7.1 8287.0
ZRECCR DIA 1504 7.0 6368.3
ZFIOBC2 DIA 852 5.8 9302.3
ZFIRP DIA 6641 5.6 1162.6
ZFIBB DIA 8592 4.0 633.4
ZFIREMTCH DIA 73 3.5 66443.6
ZRECPD DIA 8895 3.4 525.3
45.3% of the "Total DB Time" in the above table is caused by customer transactions.
DATABASE LOAD BY TRANSACTIONS (BATCH/SPOOL)
Transaction Type Dialog Steps Total DB Time in % Avg. DB Time in ms
Total 21492 100.0 71399.3
SBIE0001 BTC 36 99.5 42408448.0
RSAL_BATCH_TOOL_DISPATCHING BTC 96 0.1 21770.3
ZRE_GENERATE_COND_RO BTC 5 0.1 237287.8
ZRE_AUTO_REJECT_OFFER BTC 20 0.1 54977.8
SAPRSLOG BTC 4 0.1 257824.5
ZRE_TRANSFER_TOCONT_UPL BTC 346 0.1 2327.7
RSPO1043 BTC 4 0.0 143273.5
ZFIPR SPO 448 0.0 387.1
(BATCH) BTC 7368 0.0 22.2
ZFIADCA SPO 486 0.0 177.9
0.3% of the "Total DB Time" in the above table is caused by customer transactions.
Please advice.
Regards,
AhmedGentlemen,
Please advise me with the following scenario, which is Iu2019m facing a problem with system performance,
My system configuration is:
SAP ECC 6.0 , Oracle 10.2.0.2.0 , Kernel Patch number : 202 , DBSL Patch No. : 046
Server Configuration:
Power 6 , Processor Type: PowerPC_POWER6 , Processor Implementation Mode: POWER 6 , Processor Version: PV_6_Compat , Number Of Processors: 6 , Processor Clock Speed: 3503 MHz , CPU Type: 64-bit , Kernel Type: 64-bit , LPAR Info: 2 PRODUCTION , Memory Size: 47104 MB , Good Memory Size: 47104 MB , Platform Firmware level: EL340_039 , Firmware Version: IBM,EL340_039
My active parameter in Tcode : RZ10 as follow:
Parameter Name Parameter value
rsau/enable 1
login/failed_user_auto_unlock 0
login/fails_to_user_lock 5
gw/max_sys 2000
gw/max_overflow_size 25000000
rdisp/max_comm_entries 2000
rdisp/tm_max_no 2000
gw/max_conn 2000
rdisp/max_arq 2000
ES/SHM_SEG_COUNT 8192
ES/SHM_USER_COUNT 8192
ES/SHM_SEG_SIZE 2048
ES/TABLE SHM_SEGS
ztta/short_area 4000000
em/global_area_MB 256
zcsa/db_max_buftab 10000
sap/bufdir_entries 10000
enque/table_size 60000
rsdb/obj/large_object_size 35000
rsdb/obj/max_objects 45000
rsdb/obj/buffersize 150000
rdisp/max_wprun_time 25000
DIR_CT_RUN $(DIR_EXE_ROOT)/run
DIR_EXECUTABLE $(DIR_INSTANCE)/exe
PHYS_MEMSIZE 8000
exe/saposco $(DIR_CT_RUN)/saposcol
rdisp/wp_no_dia 70
rdisp/wp_no_btc 20
exe/icmbnd $(DIR_CT_RUN)/icmbnd
rdisp/wp_no_enq 1
rdisp/wp_no_vb 2
rdisp/wp_no_vb2 2
rdisp/wp_no_spo 10
abap/buffersize 9900000
zcsa/table_buffer_area 108003328
rtbb/buffer_length 60000
rsdb/cua/buffersize 24000
zcsa/presentation_buffer_area 28166144
rdisp/appc_ca_blk_no 2000
rdisp/wp_ca_blk_no 1000
rsdb/ntab/entrycount 68500
rsdb/ntab/ftabsize 100000
rsdb/ntab/irbdsize 20000
rsdb/ntab/sntabsize 3995
abap/use_paging 0
ztta/roll_first 1024
rdisp/keepalive_timeout 8000
ztta/roll_area 9000960
rdisp/ROLL_SHM 16384
rdisp/ROLL_MAXFS 32768
rdisp/PG_SHM 16384
rdisp/PG_MAXFS 200064
abap/heap_area_dia 2012217344
abap/heap_area_nondia 2012217344
abap/heap_area_total 2012217344
abap/heaplimit 40894464
abap/swap_reserve 20971520
ztta/roll_extension 2101346304
em/initial_size_MB 4092
em/blocksize_KB 4096
em/stat_log_size_MB 20
em/stat_log_timeout 0
install/codepage/appl_server 4102
ipc/shm_psize_10 500000000
ipc/shm_psize_14 0
ipc/shm_psize_18 0
ipc/shm_psize_19 0
ipc/shm_psize_30 -10
ipc/shm_psize_40 500000000
ipc/shm_psize_41 0
ipc/shm_psize_51 -10
ipc/shm_psize_52 -10
ipc/shm_psize_54 -10
ipc/shm_psize_55 -10
ipc/shm_psize_57 -10
ipc/shm_psize_58 -10
I already generated EWA report and I got the following result:
Performance Evaluation
The following table shows the average response times for various task types:
Task type Dialog Avg. Resp. Avg. CPU Avg. Wait Avg. Load Avg. DB Avg. GUI
DIALOG 212990 1595.2 257.7 31.0 5.0 622.2 136.8
RFC 2904 11876.4 192.1 33.1 1.4 10574.2 0.0
UPDATE 86257 116.1 28.4 2.1 2.9 58.1 0.0
UPDATE2 1100 84.6 16.9 1.3 1.4 48.2 0.0
BATCH 11600 189360.5 46218.1 5.5 3.7 132313.5 0.0
SPOOL 9989 1686.8 37.1 55.6 0.3 49.2 0.0
1.1. Current Workload
The following table lists the number of current users (measured from our workload analysis) in your system.
Low Activity Medium Activity High Activity Total Users
162 119 6 287
1.2. Performance Evaluation
Task Time Steps Avg. Response Avg. CPU Avg. Database
Dia 08-09 3726 1343 137 889
Dia 09-10 19990 1003 174 620
Dia 10-11 20603 1747 112 630
Dia 11-12 27934 2437 239 612
Dia 12-13 18921 2737 235 858
Dia 13-14 21579 2163 349 549
Dia 16-17 22529 1134 230 703
Dia 17-18 12189 1709 561 991
Dia 19-20 5840 1550 414 967
Dia 20-21 4951 1294 176 454
Task Reference for Avg. Response Time (ms) Reference for Avg. DB time (ms)
Dia 1200 600
Upd 2400 1200
HTTP 1200 600
Please advice.
Regards,
Ahmed -
Purchase order print program error
hi experts!
am facing a problem in my purchase order print program. the problem is that when i am trying to see the print preview the following dump error is throughing, which am not able to understand.
the P.O total amount should be change into words( like one million then thousand thirty three kuwait dinars)
but the total amount is not converting into as mentioned, instead the dump is encountered.
please give me solution,
thnaks
*DUMP*
Runtime Errors CONVT_NO_NUMBER
Exception CX_SY_CONVERSION_NO_NUMBER
Date and Time 05.05.2008 19:04:43
Short text
Unable to interpret "1760,778.71 " as a number.
What happened?
Error in the ABAP Application Program
The current ABAP program "ZMM_SUBROUTINES" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
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.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CONVERSION_NO_NUMBER', was not
caught in
procedure "GET_AMT_IN_WORDS" "(FORM)", nor was it propagated by a RAISING
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:
The program attempted to interpret the value "1760,778.71 " as a number, but
since the value contravenes the rules for correct number formats,
this was not possible.
How to correct the error
Whole numbers are represented in ABAP as a sequence of numbers, possibly
with an algebraic sign.
The following are the possibilities for the representation of floating
point numbers:
[algebraic sign][mantissa]E[algebraic sign][exponent]
[algebraic sign][whole number part].[fraction part]
For example, -12E+34, +12E-34, 12E34, 12.34
If the error occurred in your own ABAP program or in an SAP
program you modified, try to remove the error.
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:
"CONVT_NO_NUMBER" "CX_SY_CONVERSION_NO_NUMBER"
"ZMM_SUBROUTINES" or "ZMM_SUBROUTINES"
"GET_AMT_IN_WORDS"
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.
The exception must either be prevented, caught within proedure
"GET_AMT_IN_WORDS" "(FORM)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "EHPAP1"
Network address...... "10.100.150.103"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "00C3B3F04C00"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "EHPDB"
Database type..... "DB6"
Database name..... "EHP"
Database user ID.. "SAPEHP"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Mar 19 2007 20:40:49"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "DB6_81 "
Patch level. 102
Patch text.. " "
Database............. "DB6 08.02., DB6 09."
SAP database version. 700
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory consumption
Roll.... 16192
EM...... 29328936
Heap.... 0
Page.... 1359872
MM Used. 19180992
MM Free. 1764848
User and Transaction
Client.............. 400
User................ "FADISULAIMAN"
Language key........ "E"
Transaction......... "ME22N "
Program............. "ZMM_SUBROUTINES"
Screen.............. "SAPLMEGUI 0014"
Screen line......... 22
Information on where terminated
Termination occurred in the ABAP program "ZMM_SUBROUTINES" - in
"GET_AMT_IN_WORDS".
The main program was "RM_MEPO_GUI ".
In the source code you have the termination point in line 398
of the (Include) program "ZMM_SUBROUTINES".
The termination is caused because exception "CX_SY_CONVERSION_NO_NUMBER"
occurred in
procedure "GET_AMT_IN_WORDS" "(FORM)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "ZMM_SUBROUTINES "; its source code begins in line
358 of the (Include program "ZMM_SUBROUTINES ".
Source Code Extract
Line SourceCde
368 DATA: lt_spell LIKE spell.
369
370 READ TABLE in_tab WITH KEY 'CURR'.
371 IF sy-subrc = 0.
372 lf_curr = in_tab-value.
373 ENDIF.
374
375 READ TABLE in_tab WITH KEY 'NETWR'.
376 IF sy-subrc = 0.
377 lf_netpr_01 = in_tab-value.
378 REPLACE ',' IN lf_netpr_01 WITH ' '.
379 CONDENSE lf_netpr_01 NO-GAPS.
380
381 IF lf_curr = 'KWD'.
382 lf_netpr_kwd = lf_netpr_01.
383
384 CALL FUNCTION 'SPELL_AMOUNT'
385 EXPORTING
386 amount = lf_netpr_kwd
387 currency = lf_curr
388 filler = ''
389 language = sy-langu
390 IMPORTING
391 in_words = lt_spell
392 EXCEPTIONS
393 not_found = 1
394 too_large = 2
395 OTHERS = 3.
396
397 ELSE.
>>>>> lf_netpr = lf_netpr_01.
399 CALL FUNCTION 'SPELL_AMOUNT'
400 EXPORTING
401 amount = lf_netpr
402 currency = lf_curr
403 filler = ''
404 language = sy-langu
405 IMPORTING
406 in_words = lt_spell
407 EXCEPTIONS
408 not_found = 1
409 too_large = 2
410 OTHERS = 3.
411 ENDIF.
412 IF sy-subrc <> 0.
413 * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
414 * WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
415
416 ELSE.
417
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 17
SY-TABIX 1
SY-DBCNT 18
SY-FDPOS 1
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY NORMAL
SY-UCOMM PREVOUTPUT
SY-TITLE Held Imp. Pur. O r - ESG 5000000021 Created by Fadi Sulaiman
SY-MSGTY A
SY-MSGID TD
SY-MSGNO 426
SY-MSGV1 NEXTPAGE
SY-MSGV2 ZMEDRUCK_PO
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20080505
SY-UZEIT 190441
SY-XPROG SAPCNVE
SY-XFORM CONVERSION_EXITHi Prasad,
Check the FM's
SPELL_AMOUNT --> for display in millions
HR_IN_CHG_INR_WRDS --> for display in lakhs and crores -
Getting Dump CALL_FUNCTION_SYSCALL_ONLY
Hi Expert ,
while finished the SM:SELFDIAGNOSIS this job in Solution manager system so in that moment i'm getting a CALL_FUNCTION_SYSCALL_ONLY dump in quality server.
Runtime Errors CALL_FUNCTION_SYSCALL_ONLY
Date and Time 25.08.2011 01:43:31
Short text
You are not authorized to logon to the target system (error code 0).
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSYST" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
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.
Error analysis
RFC calls (Remote Function Calls) were sent with the invalid user
ID "DDIC ". The receiving system regarded the first call as a system
call and therefore accepted it without a valid user ID.
However, the last call was to an external function module and
was thus rejected.
The action was carried out by caller "DDIC " with client 100 from within
system "SOL " and transaction " ".
How to correct the error
In the trusted relation, a logon failure can be caused either by the
fact that the entered security key for system "SOL " is invalid or that the
trusted system data has lost its validity due to a timeout.
The error code of the trusted system was 2.
Meaning:
0 Correct logon as trusted system mode
1 No trusted system entry for the caller system "SOL " or the
security key entry for system "SOL " is invalid
2 User "DDIC " has no RFC authorization (authorization object
S_RFCACL) for caller "DDIC " with client 100.
3 The timestamp of the logon data is invalid
The error code of the SAP logon procedure was 0.
Meaning:
0 Logon was correct
1 Wrong password or invalid user ID
2 User is locked
3 Too many logon attempts
Runtime Errors CALL_FUNCTION_SYSCALL_ONLY
D ate and Time 25.08.2011 01:43:31
5 Error in authorization buffer (internal error)
6 No external user check
7 Invalid user type
8 Validity period of user exceeded
System environment
SAP-Release 701
Application server... "QAserver"
Network address...... "192.168.1.6"
Operating system..... "AIX"
Release.............. "6.1"
Hardware type........ "000A154AD400"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "QAserver"
Database type..... "DB6"
Database name..... "QAS"
Database user ID.. "SAPQAS"
Terminal.......... " "
Char.set.... "C"
SAP kernel....... 701
created (date)... "Sep 23 2010 21:55:35"
create on........ "AIX 2 5 00CB5A5B4C00"
Database version. "DB6_81 "
Patch level. 111
Patch text.. " "
Database............. "DB6 08.02., DB6 09."
SAP database version. 701
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6, AIX 1 7"
Memory consumption
Roll.... 16192
EM...... 4189848
Heap.... 0
Page.... 0
MM Used. 1226088
MM Free. 2961160
User and Transaction
Client.............. 000
User................ "SAPSYS"
Language Key........ "E"
Transaction......... " "
Transactions ID..... "858DCEE0F1E5F1B3AAFCE61F137E15A3"
Program............. "SAPLSYST"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Runtime Errors CALL_FUNCTION_SYSCALL_ONLY
D ate and Time 25.08.2011 01:43:31
Information on caller of Remote Function Call (RFC):
System.............. "SOL"
Database Release.... 701
Kernel Release...... 701
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "synchron and non-transactional (emode 0, imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........." "
Outbound Queue Name.." "
Client.............. 100
User................ "DDIC"
Transaction......... " "
Call Program........."CL_DSMOP_RFC_WATCHER==========CP"
Function Module..... "RFCPING"
Call Destination.... "SM_QASCLNT100_TRUSTED"
Source Server....... "solid_SOL_01"
Source IP Address... "192.168.1.2"
Additional information on RFC logon:
Trusted Relationship "X"
Logon Return Code... 0
Trusted Return Code. 2
Note: For releases < 4.0, information on the RFC caller are often
only partially available.
Information on where terminated
Termination occurred in the ABAP program "SAPLSYST" - in "TABLE_COMPRESS".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 67
of the (Include) program "SAPMSSY1".
Source Code Extract
Line SourceCde
37 endmodule.
38
39 module %_rfcdia_call output.
40 "Do not display screen !
41 call 'DY_INVISIBLE_SCREEN'.
42 perform remote_function_diacall.
43 endmodule.
44
45 module %_cpic_start.
46 if sy-xprog(4) = '%RFC'.
47 perform remote_function_call using rfctype_external_cpic.
48 else.
49 call 'APPC_HD' id 'HEADER' field header id 'CONVID' field convid.
50 perform cpic_call using convid.
51 endif.
52 endmodule.
53
54
Runtime Errors CALL_FUNCTION_SYSCALL_ONLY
D ate and Time 25.08.2011 01:43:31
55 form cpic_call using convid type c.
56 communication send id convid buffer header.
57 if sy-subrc eq 0.
58 perform (sy-xform) in program (sy-xprog).
59 else.
60 message a800.
61 endif.
62 endform.
63
64 form remote_function_call using value(type).
65 data rc type i value 0.
66 do.
>>>>> call 'RfcImport' id 'Type' field type.
68 if sy-xprog = 'JAVA'.
69 system-call plugin
70 id 'JAVA' value 'FORW_JAVA'
71 id 'RC' value rc.
72 * if there is no rollout on the JAVA side which
73 * rolls both, JAVA and ABAP, we return to the
74 * C-Stack and reach this point
75
76 * in case there was an rollout, the ABAP-C stack is lost
77 * and we jump direkt to this point
78
79 * here we trigger the rollout on this Abap side with
80 * the following statement
81 system-call plugin
82 id 'JAVA' value 'ROLL_OUT'
83 id 'RC' value rc.
84 else.
85 perform (sy-xform) in program (sy-xprog).
86 rsyn >scont sysc 00011111 0.
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 2
SY-TABIX 0
SY-DBCNT 1
SY-FDPOS 0
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE CPIC and RFC Control
SY-MSGTY
SY-MSGID
SY-MSGNO 000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20110825
SY-UZEIT 014330
SY-XPROG SAPLSYST
Runtime Errors CALL_FUNCTION_SYSCALL_ONLY
D ate and Time 25.08.2011 01:43:31
SY-XFORM RFCPING
Active Calls/Events
No. Ty. Program Include Line
Name
2 FORM SAPMSSY1 SAPMSSY1 67
REMOTE_FUNCTION_CALL
1 MODULE (PBO) SAPMSSY1 SAPMSSY1 30
%_RFC_START
Chosen variables
Name
Val.
No. 2 Ty. FORM
Name REMOTE_FUNCTION_CALL
%_DUMMY$$
0000
0000
2222
0000
SY-REPID
SAPMSSY1
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454555322222222222222222222222222222222
310D339100000000000000000000000000000000
SYST-REPID
SAPMSSY1
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454555322222222222222222222222222222222
310D339100000000000000000000000000000000
HEADER
000000000000
000000000000
TYPE
3
0000
0003
SY-XPROG
SAPLSYST
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454555522222222222222222222222222222222
310C393400000000000000000000000000000000
%_ARCHIVE
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Runtime Errors CALL_FUNCTION_SYSCALL_ONLY
D ate and Time 25.08.2011 01:43:31
RC
0
0000
0000
SY-XFORM
RFCPING
000000000000000000000000000000
000000000000000000000000000000
544544422222222222222222222222
26309E700000000000000000000000
%_SPACE
0
0
2
0
No. 1 Ty. MODULE (PBO)
Name %_RFC_START
%_PRINT
000 0###
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
RFCTYPE_INTERNAL
3
0000
0003
Internal notes
The termination was triggered in function "PrepareSignOnRabax"
of the SAP kernel, in line 5385 of the module
"//bas/701_REL/src/krn/rfc/abrfcfun.c#13".
The internal operation just processed is "CALY".
Internal mode was started at 20110825014330.
The called function module was "RFCPING ".
Caller system......: "SOL "
Caller.............: "DDIC "
Caller client......: 100
RFC user ID........: "DDIC "
RFC client.........: 100
Transaction code...: " "
Logon return code..: 0
Trusted return code: 2
Note: For releases < 4.0, information on the caller may not exist
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit = unlimited
=> Stack limit = 4294967296
=> Core limit = 1073741312
=> File size limit = unlimited
Runtime Errors CALL_FUNCTION_SYSCALL_ONLY
D ate and Time 25.08.2011 01:43:31
=> Heap address = 0x0x11cd64d20
=> Stack address = 0xfffffffffff4850
=> Stack low = 0xfffffffffff4850
=> Stack high = 0xffffffffffff810
=> Stack Trace:
AixStack() at 0x10007fd28
CTrcStack2() at 0x10007fe20
rabax_CStackSave__Fv() at 0x100068b10
ab_rabax() at 0x1000650a4
PrepareSignOnRabax() at 0x100e3beb0
ab_rfcimport() at 0x100e3a7e4
ab_jcaly__Fv() at 0x10005aeb8
ab_extri__Fv() at 0x10052701c
ab_xevent__FPCUs() at 0x100a31b84
ab_dstep() at 0x100805368
dynpmcal() at 0x100d7f2b4
dynppbo0() at 0x100d7cdf8
dynprctl() at 0x100d84bc4
dynpen00() at 0x100d786a8
Thdynpen00() at 0x10009b01c
TskhLoop() at 0x10009ffa8
ThStart() at 0x1000b7dd0
DpMain() at 0x1015518ec
nlsui_main() at 0x101a4b620
List of ABAP programs affected
Index Typ Program Group Date Time Size Lang.
0 Prg SAPMSSY1 0 11.04.2005 09:27:15 21504 E
1 Prg SAPLSRFC 1 17.12.2008 07:36:53 43008 E
2 Prg SAPRFCSL 0 13.02.2005 17:31:45 17408 E
3 Typ RFCSYSACL 0 13.02.2005 17:31:45 7168
4 Prg SAPLSYST 4 29.11.2010 01:19:16 35840 E
5 Typ SYST 0 09.09.2004 14:18:12 31744
Directory of Application Tables
Name Date Time Lngth
Val.
Program SAPMSSY1
SYST . . : : 00004612
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0\0\0
Program SAPRFCSL
RFCSYSACL . . : : 00001760
SOL QAS
Please assist me asap.
Regards
Shubh
Edited by: Shiv ji Mishra on Sep 17, 2011 9:38 AMHello,
It seems some trusted RFC issue. Check the RFCs, somewhere it might be possible that the DDIC user is being used and it doesn't have proper RFC authorization. Try to use some different user.
See the extract from the dump
The action was carried out by caller "DDIC " with client 100 from within system "SOL " and transaction " ". How to correct the error In the trusted relation, a logon failure can be caused either by the fact that the entered security key for system "SOL " is invalid or that the trusted system data has lost its validity due to a timeout. The error code of the trusted system was 2. Meaning: 0 Correct logon as trusted system mode 1 No trusted system entry for the caller system "SOL " or the security key entry for system "SOL " is invalid 2 User "DDIC " has no RFC authorization (authorization object S_RFCACL) for caller "DDIC " with client 100
Thanks -
Hi,
I getting below error while starting dbca on oracle version 11.1.0.6
$ dbca
Exception in thread "main"My Oracle is running on AIX 6.1 and all the necessary OS patches were installed before proceeding with new Oracle installation.
All the environment variables are set properly, I am able to see the GUI of "netca" & "xclock" from same prompt.
Also there were no errors reported during oracle installation.
Please suggest what could be the cause.
Thanks for your time.Hope all the binaries are linked?? crosscheck..with opatch lsinventroy -all
% env | grep PATH --make sure you are on the correct PATH for executing dbca....
% which dbca - will give you the path linked to...can give idea if missing out earlier...
--Raman. -
Oracle 11.2.0.2 Patch 10040035 and PSU
Hi guys,
i'm looking fot the Patch 10040035, it is in Patchset 11.2.0.3, but this patchset is not available for AIX.
It is available as one off patch for 11.2.0.2 but is not in any PSU, does anybody know why?
My customer has his own processes for implement Patches. It ist easier to install a PSU as a one off patch.
regards
Frankuser580866 wrote:
Hi guys,
i'm looking fot the Patch 10040035, it is in Patchset 11.2.0.3, but this patchset is not available for AIX.
It's probably a question of days, it was promised for Oct. 2011.
Nicolas.
Maybe you are looking for
-
ADF Desktop Integration: How do I use dependent LOVs in Table Components?
Hi, I have a table component that has a series of dependent LOVs. Now, while I understand that ADFdi allows for LOVs to be chained together by dependency, what I don't understand is how to get the child values to change based on a selection of a pare
-
Does anyone know a way to stream audio from Snow Leopard to a PPC running Panther?
I have recently aquired a iMac PPC, I've freshly installed Panther on it and it runs a treat. I was wondering however if there is a way to stream audio from my main Desktop, a 2007 iMac running Snow Leopard. iTunes library share isn't a solution eith
-
Hi We are getting Warning notification in solution manager saying ' The transport target is not the project transport target. Continue, or Cancel release and change transport target? COuld you please throw some light on what this Warning is all about
-
Side-stepping protected songs for Toast burn?
I'm trying to burn an audio DVD in Toast by simply importing a 71 song playlist from iTunes. For the majority of songs, I get a message that says something like "You can only burn these songs in iTunes". I'm assuming this is because of the rediculous
-
Function Module to calculate pallets
Hi, I need a Function Module to calculate pallets for free of charge articles while creating a sales order. can someone name any FM for this purpose. Thanks in advance