during spam update, it is throwing short dump "CALL_FUNCTION_PARM_UNKNOWN"

[Former Member]

Hello All,

We updated spam to latest(50),however it is throwing dump and could not restart spam. It throws dump every time we execute spam. Kindly provide

a solution for the same. Pls find screenshot of the dump.

Runtime Errors         CALL_FUNCTION_PARM_UNKNOWN

Except.                CX_SY_DYN_CALL_PARAM_NOT_FOUND

Date and Time          16.10.2013 10:04:56

Short text

    Function parameter "ET_COMPONENTS" is unknown.

Please provide the solution as same..

Regards,

Varun.Ch

[Former Member]

Hi,

Go through the following Sap note,

Note 822379 - Known problems with Support Packages in SAP NW 7.0x AS ABAP

Thanks,

Chetan

[Former Member]

Hello All,

We trying to restart , but while hit tcode Spam. It's getting dump.

I unable to access Tcode Spam..

Dump:

Runtime Errors         CALL_FUNCTION_PARM_UNKNOWN
Except.                CX_SY_DYN_CALL_PARAM_NOT_FOUND
Date and Time          16.10.2013 10:04:56

Short text
     Function parameter "ET_COMPONENTS" is unknown.

What happened?
     Error in the ABAP Application Program

     The current ABAP program "CL_OCS_ENVIRONMENT============CP" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.

     Function module "OCS_GET_INSTALLED_COMPS" was called
     with the parameter "ET_COMPONENTS".
     This parameter is not defined.

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.

ror analysis
  An exception occurred that is explained in detail below.
  The exception, which is assigned to class 'CX_SY_DYN_CALL_PARAM_NOT_FOUND', was
   not caught in
  procedure "SET_CURRENT_ENVIRONMENT" "(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:
  Function module "OCS_GET_INSTALLED_COMPS" was called
  with the parameter "ET_COMPONENTS".
  This parameter is not defined.

w 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:

  "CALL_FUNCTION_PARM_UNKNOWN" "CX_SY_DYN_CALL_PARAM_NOT_FOUND"

"CL_OCS_ENVIRONMENT============CP" or "CL_OCS_ENVIRONMENT============CM002"
"SET_CURRENT_ENVIRONMENT"

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
"SET_CURRENT_ENVIRONMENT" "(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... "POVSRBUSAPBI"
    Network address...... "192.168.215.202"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "AMD64 Level 6 ("
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 8
    Shortdump setting.... "full"

    Database server... "POVSRBUSAPBI"
    Database type..... "ORACLE"
    Database name..... "BID"
    Database user ID.. "SAPSR3"

    Terminal.......... "INFCHCIT014"

    Char.set.... "C"

    SAP kernel....... 720
    created (date)... "Jan 16 2013 16:56:16"

    Patch level. 401
    Patch text.. " "

    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
    SAP database version. 720
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
     NT 6.0, Windows NT 6.1, Windows NT 6.2"

    Memory consumption
    Roll.... 0
    EM...... 8379584
    Heap.... 0
    Page.... 0
    MM Used. 1545424
    MM Free. 2641696

User and Transaction

    Client.............. 000
    User................ "BIDADM"
    Language key........ "E"
    Transaction......... "SPAM "
    Transactions ID..... "4B1C36E321F2F10FA489005056A70026"

    Program............. "CL_OCS_ENVIRONMENT============CP"
    Screen.............. "SAPMSPAM 0100"

    Screen line......... 12

Information on where terminated
    Termination occurred in the ABAP program "CL_OCS_ENVIRONMENT============CP" -
     in "SET_CURRENT_ENVIRONMENT".
    The main program was "SAPMSPAM ".

    In the source code you have the termination point in line 45
    of the (Include) program "CL_OCS_ENVIRONMENT============CM002".
    The termination is caused because exception "CX_SY_DYN_CALL_PARAM_NOT_FOUND"
     occurred in
    procedure "SET_CURRENT_ENVIRONMENT" "(METHOD)", but it was neither handled
     locally nor declared
    in the RAISING clause of its signature.

    The procedure is in program "CL_OCS_ENVIRONMENT============CP "; its source
     code begins in line
    1 of the (Include program "CL_OCS_ENVIRONMENT============CM002 ".

Source Code Extract

Line  SourceCde

   15     FIELD-SYMBOLS: <fs_component> TYPE comp_props.
   16-------------------------------------------

Regards,

[Former Member]

Hi Varun,

Please check the below forum.

http://scn.sap.com/thread/3395730

They mentioned like need to change the repository changes in SCC4 and retry.

Regards,

Raja. G

[Former Member]

Hi,

First of all please check that if OCS_GET_INSTALLED_COMPS fonctuon module is there and you can see the parameter ET_COMPONENTS

Try to activate it if it doesn't helps you can try this below. But i would use the below method once sap says ok to go ahead with it.

1-Ensure that no more TP and R3trans are running at OS level

2- Ensure that the entry in the transport buffer for SPAM package is still available, check that with

tp showbuffer <SID> pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL tag=spam

If the entry of SAPM package is still available, ensure that TRBAT and TRJOB tables are empty (check at DB level)

3- then start the main import manually using the command

tp r3i spam package SID pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL tag=spam

-Dclientcascade=yes -Drepeatonerror=8

Thanks

Rishi Abrol .

[Former Member]

Hi Rishi,

As discuused above, I tryed ... But i'm getting below thing..

E:\usr\sap\trans\buffer>tp showbuffer BID pf=/usr/sap/trans/bin/TP_DOMAIN_BID.PF
L tag=spam
tp=>sapparam(1c): No Profile used.
tp=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
This is tp version 380.04.07 (release 720, unicode enabled)

BID buffer:

BIDK901113          |                    | |will not be imported because it is n
ot tagged.
BIDK901109          |                    | |will not be imported because it is n
ot tagged.
BIDK901106          |                    | |will not be imported because it is n
ot tagged.
BIDK901104          |                    | |will not be imported because it is n
ot tagged.
BIDK901102          |                    | |will not be imported because it is n
ot tagged.
BIDK901096          |                    | |will not be imported because it is n
ot tagged.

TASK                |PROJECT             |P|CMD Im|DD Im |DD Act|MainIm|ADO Im|V
ersFl|Deploy|XPRA  |ChkDpl|Gener |UMODE|TAGS
--------------------+--------------------+-+------+------+------+------+------+-
-----+------+------+------+------+-----+----
SAPKD70150          |                    | |*0012 |*0004 |*0004 |*0012 |      |
     |      |6     |      |      |     |D

that makes 1 transport to be imported.

tp finished with return code: 0
meaning:
  Everything OK

E:\usr\sap\trans\buffer>cd ..

E:\usr\sap\trans>tp r3i SAPKD70150 BID pf=/usr/sap/trans/bin/TP_DOMAIN_BID.PFL t
ag=spam -Dclientcascade=yes -Drepeatonerror=8
tp=>sapparam(1c): No Profile used.
tp=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
This is tp version 380.04.07 (release 720, unicode enabled)
This is R3trans.exe version 6.23 (release 720 - 31.10.12 - 20:12:06).
unicode enabled version
R3trans=>sapparam(1c): No Profile used.
R3trans=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
2EETW000 sap_dext called with msgnr "1":
2EETW000 ---- db call info ----
2EETW000 function:   db_dynpro_interface
2EETW000 fcode:      DI_MODIFY
2EETW000 tabname:    SFIELDS
2EETW000 len (char): 44
2EETW000 key:        SAPLOCS_ALV_UI                          0300
2EETW000 retcode:    1
2EETW000 sql error:  0
R3trans.exe finished (0012).
ERROR: stopping on error 12 during MAIN IMPORT
stopping on error 12 during MAIN IMPORT

tp returncode summary:

TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
  A tool used by tp aborted

------------------------

Please suggest as same..

Regards,

Varun

[Former Member]

Hi,

What happens when you run SPAM now.

If still same error. Try to download the latest tp,R3trans from service market place and see if it helps you and then restart the sap system and try to import the spam  again in sap.

Else i would say to contact sap.

Thanks

Rishi Abrol

[Former Member]

Rishi,

Still getting same Dump..

And Now we getting another error.

----------------------------------------------------------

4 ETW000  [     dev trc,00000]     OCILobWrite2() failed with SQL error 8103:                            247  16.170818

4 ETW000  [     dev trc,00000]     ORA-08103: object no longer exists                                                                                       

4 ETW000                                                                                                 226  16.171044

4 ETW000  [     dev trc,00000]     OCILobWrite2(con=0, BLOB locp=0A362858, bufp=0AB84090, bufl=65536, 1=FIRST_PIECE, amt=65536) -> orc=8103

4 ETW000                                                                                                 275  16.171319

4 ETW000  [     dev trc,00000]  used+free LL chunks: num=2+0, cnt=0+0, max=2+0; all locators: Lb.cnt=2, Lb.max=20, Lb.itp=0000NULL

4 ETW000                                                                                                 205  16.171524

4 ETW000  [    dbsloci.,00000]  *** ERROR => ORA-08103 occurred when writing to a LOB                     90  16.171614

4 ETW000  [     dev trc,00000]  Dump statement cache:                                                    143  16.171757

4 ETW000  [     dev trc,00000]  sc_p=00000000028426B0,no=46,idc_p=000000000285DCD0,con=0,act=1,slen=128,smax=256,#vars=4,stmt=000000000A3C6F50,table=DYNPSOURCE

--------------------------------------------------------------------------------------------

Please ADVICE ME AS SAME..

Regards,

Varun.Ch

[Former Member]

Hi Varun ,

Raise a high priority case with SAP and open the  telnet/R3 support connections

Regards

Ram

[Former Member]

Hi Ram/Rishi,

I Already Done, But those people says, Restore old backup like that..

But we didn't have recent backup.... that's what... 😞

I'm looking for without restore option... 😞

Regards,

Varun

[Former Member]

Hi,

Please check the below file.

Note 1738448 - ORA-08103 during INSERT/UPDATE into LOB basicfiles

Thanks

Rishi abrol

[Former Member]

Hi,

But you can ask for option what was the cause of it and how it will not happen again if i import it.

thanks

Rishi Abrol

[Former Member]

Hi,

Kindly check the TP profile, error would be transport profile.

Kindly check the tp call -> DB connect status.

Kindly check TP profile -> Version.

aslo check the domain status.

BR,

Prabhakar

[Former Member]

Please attach the full dump information to messsage.

[AtulKumarJain]

Hi Varun,

Please try to rerun the spam update mostly it will work.

Please run and update us.

BR

atul

[Former Member]

Hi Varun,

Refer the below sap notes ::

Note 1597767 - Known problems with Support Packages in SAP NW 7.3 AS ABAP

Note 1597765 - Known problems with Support Packages in SAP NW 7.31 AS ABAP

Note 831925 - Short dump CX_SY_DYN_CALL_PARAM_NOT_FOUND & more

Regards

Ram