Hi,
Could you share memory configurations for the system.
malloc failed
Please follow SAP Note 217351 - No free memory of class PERM available/Malloc failed
& tune parameters mentioned in it.
Regards,
Gaurav
Hi,
Could you share memory configurations for the system.
malloc failed
Please follow SAP Note 217351 - No free memory of class PERM available/Malloc failed
& tune parameters mentioned in it.
Regards,
Gaurav
Hi Sufaid
Thanks for you info
Restart the full system and then check the same phase. and also attach the dump as text format.
BR
SS
Hi Sufaid ,
If i were you i will do the following
1 Stop Sum tool . Take a backup of your SUM directory and if Possible the DB .
2 . Apply manually the corrections mentioned in SAP Note 1160105 in the main instance .
3. Start SUM tool and Try once again
Thanks ,
Manu
Current Date | 12.02.2015 |
Time | 15:33:37 |
Application Server | ASBWSBOX_B12_00 |
User Name | DDIC |
Client ID | 000 |
Keep | C |
Name of runtime error | CREATE_DATA_UNKNOWN_TYPE |
Exception | CX_SY_CREATE_DATA_ERROR |
Index of Work Process | 10 |
Transaktions-ID | F7AAB2E40D90F1A89AD7002219537AE5 |
Runtime Errors CREATE_DATA_UNKNOWN_TYPE
Exception CX_SY_CREATE_DATA_ERROR
Date and Time 12.02.2015 15:33:37
Short text
CREATE DATA: The specified type "/BI0/APERS_BOD00" is no valid data type.
What happened?
Error in the ABAP Application Program
The current ABAP program "RS_PERS_XPRA_1" had to be terminated because it
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_CREATE_DATA_ERROR', was not
caught and
therefore caused a runtime error.
The reason for the exception is:
The dynamically specified type "/BI0/APERS_BOD00" at CREATE DATA is no valid
data type.
The type is either unknown or an object type.
How to correct the error
If the specified type "/BI0/APERS_BOD00" is an object type, then new objects of
this
type (instances) are not created with CREATE DATA, but with
CREATE OBJECT.
If the type is unknown, then it must be created in the program or in the
ABAP dictionary.
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:
"CREATE_DATA_UNKNOWN_TYPE" "CX_SY_CREATE_DATA_ERROR"
"RS_PERS_XPRA_1" or " "
"START-OF-SELECTION"
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.
Hi Sriram
I attached the text and i tried by doing the full restart as well.
Thanks
Sufaid
Hi Sufaid
You can follow the SAP note 2075289 solutions. same error message in Solution manager 7.1 BW area.
BR
SS
I can see in rfc trace that wrong password for ddic put how can I find the rfc with the wrong password?
You need to first see why the ddic user is getting locked .
Is the RDDIMPDMP job getting sheduled ( ststus ) just after you click on the transport truck ?
check whether the report is scheduled to run under any user .if yes delete all of them .
Reschedule it using se38 in 000 DDIC user ( or any user with full authorizations temporarly ) with normal priority
Thanks ,
Manu
I can't find the rfc that is locking ddic.
The only thing in the log is
***LOG US1=> Login, Wrong Password (DDIC ) [sign.c 4836]
Did you check all your RFC connections ( SM59 ) ?
Alternative ,
Copy the user DDIC to a new user and Schedule the report using this user . You may continue your troubleshooting of the DDIC user and reschedule once the user locking issue is fixed
Thanks ,
Manu
Cant do that it must be user didc :-(
Is the DDIC user getting locked in 000 or all the clients . Why dont you schedule the job from your main client if the DDIC is not locked there
11677 - Transports with event-controlled RDDIMPDP
34964 - New RDDIMPDP features in Release 3.0
Thanks ,
Manu
Hi Daniel
Could you refer the Microsoft blogs about this error message
Regards
Sriram
Hello,
I am compressing our ECC 6.0 DB and the initial size is 900 GB.
I am using mscompress and I expect to reduce more than 50%
the main question is: after finished the compress step, should I run the dbshrinkdb command?
I can find any note or reference to this point..
regards
Romel Rodríguez
Hi Romel ,
Please read the following note and the note contains an attached PDF as well
1488135 - Database compression for SQL Server
Thanks,
Manu
Manu, thank you for your answer
I already read it, actually, was my first read.
But, at the filesystem the .mdf files are on the same size as was in the beginning
I think this could be the answer
regards
Hi Guys,
In my DEV environment if I go to the transaciton DB02 I saw three database files in red. How can I resolve this?
Those database files have the autogrow feature setup already in the SQL Server 2008 database as displayed in the screenshots below. Also, the server have enough space.
Please let me know how can I fix this to have these three files in green.
Thanks!
Hi,
Could you check with SCN thread No free space in file
and follow steps as recommended by SivaKumar Kilari
Regards,
Hi Gaurav.
Thanks for your answer!
I'm new with SQL Server databases, could you explain me please how the initial size works? For example, could I assign to it like 20480MB if I would like to assign 20GB more to increase the space in those database files and that is going to resolve the issue? I read in others forums that I should have all the databases with the same size so I should assign 20gb more to all the database files that I have in this system?
Regards,
Carlos