Hi , Experts
I would like to setting up ERP system and already know install it with IDES.
but this time, I have to install ERP system on Netweaver 730 that is already installed. (only netweaver)
should I install ERP with SAP Upgrade Master?
please give me some help or related notes
Thanks
Hi SAP Experts
How can we fix the error ?
Please help how can we resolve the error. This is SPAU transport , we | |||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SHADOW IMPORT ERRORS and RETURN CODE in XXXK900053.KTR
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
4 ETW000 0 entries from SMODISRC~ (CUFUGR/OPT/VIM_FG1 FUNC/OPT/VIM_GET_ACTIVITY_NO %) deleted.
4 ETW000 0 entries from SMODISRC~ (PRFUGR/OPT/VIM_FG1 FUNC/OPT/VIM_GET_ACTIVITY_NO %) deleted.
4 ETW000 0 entries from SMODISRC~ (SVFUGR/OPT/VIM_FG1 FUNC/OPT/VIM_GET_ACTIVITY_NO %) deleted.
4 ETW000 0 entries from SMODISRC~ (FLFUGR/OPT/VIM_FG1 FUNC/OPT/VIM_GET_ACTIVITY_NO %) deleted.
4 ETW000 0 entries from SMODISRC~ (CIFUGR/OPT/VIM_FG1 FUNC/OPT/VIM_GET_ACTIVITY_NO %) deleted.
2EETW165 Function "/OPT/VIM_GET_ACTIVITY_NO (/OPT/VIM_FG1|24)" does not fit into the existing function group "(/OPT/VIM_FG1|23)".
4 ETW000 12 entries from SMODISRC~ (SVFUGR/OPT/VIM_VD7_BPF FUNC/OPT/VIM_START_DOC_PROCESS_ICC %) deleted.
4 ETW690 COMMIT "108132" "109620"
4 ETW000 12 entries for SMODISRC~ inserted (SVFUGR/OPT/VIM_VD7_BPF FUNC/OPT/VIM_START_DOC_PROCESS_ICC).
4 ETW000 0 entries from SMODISRC~ (FLFUGR/OPT/VIM_VD7_BPF FUNC/OPT/VIM_START_DOC_PROCESS_ICC %) deleted.
4 ETW000 0 entries from SMODISRC~ (CIFUGR/OPT/VIM_VD7_BPF FUNC/OPT/VIM_START_DOC_PROCESS_ICC %) deleted.
2EETW165 Function "/OPT/VIM_START_DOC_PROCESS_ICC (/OPT/VIM_VD7_BPF|07)" does not fit into the existing function group "(/OPT/VIM_ICC|11)".
4 ETW000 0 entries from SMODISRC~ (CUFUGR/OPT/VIM_FG1 FUNC/OPT/VIM_GET_ACTIVITY_NO %) deleted.
4 ETW000 0 entries from SMODISRC~ (PRFUGR/OPT/VIM_FG1 FUNC/OPT/VIM_GET_ACTIVITY_NO %) deleted.
4 ETW000 0 entries from SMODISRC~ (SVFUGR/OPT/VIM_FG1 FUNC/OPT/VIM_GET_ACTIVITY_NO %) deleted.
4 ETW000 0 entries from SMODISRC~ (FLFUGR/OPT/VIM_FG1 FUNC/OPT/VIM_GET_ACTIVITY_NO %) deleted.
4 ETW000 0 entries from SMODISRC~ (CIFUGR/OPT/VIM_FG1 FUNC/OPT/VIM_GET_ACTIVITY_NO %) deleted.
2EETW165 Function "/OPT/VIM_GET_ACTIVITY_NO (/OPT/VIM_FG1|24)" does not fit into the existing function group "(/OPT/VIM_FG1|23)".
4 ETW000 12 entries from SMODISRC~ (SVFUGR/OPT/VIM_VD7_BPF FUNC/OPT/VIM_START_DOC_PROCESS_ICC %) deleted.
4 ETW690 COMMIT "108188" "267868"
4 ETW000 12 entries for SMODISRC~ inserted (SVFUGR/OPT/VIM_VD7_BPF FUNC/OPT/VIM_START_DOC_PROCESS_ICC).
4 ETW000 0 entries from SMODISRC~ (FLFUGR/OPT/VIM_VD7_BPF FUNC/OPT/VIM_START_DOC_PROCESS_ICC %) deleted.
4 ETW000 0 entries from SMODISRC~ (CIFUGR/OPT/VIM_VD7_BPF FUNC/OPT/VIM_START_DOC_PROCESS_ICC %) deleted.
2EETW165 Function "/OPT/VIM_START_DOC_PROCESS_ICC (/OPT/VIM_VD7_BPF|07)" does not fit into the existing function group "(/OPT/VIM_ICC|11)".
1 ETP111 exit code : "8"
SAP Technical Upgrade Essentials and considerations
Upgrade Driving Factor:
SAP version / Enhancement Pack upgrade generally required on below scenario:
These are the primary driving factor for any SAP Upgrades.
Planning, Pre-requisite and Prior activities:
Following consideration is required for any successful upgrade within feasible timeline:
Infrastructure and platform study needs to done using the SAP product availability matrix (PAM). Using SAP PAM we can check the availability of newer SAP on specific OS and Database version. Below attached is the sample screenshot of SAP PAM (https://service.sap.com/pam).
To know any upgrade dependencies between systems in SAP landscape SAP UDA online tool can be used to check SAP component dependency. SAP UDA tool is accessible via two ways:
This will help in:
Below sample dependencies can be generated using SAP UDA tool.
Using above results we can develop phasing concept in upgrade phase. We need carry out an analysis of the systems to be upgraded to determine the inter-dependency between the various system components to be upgraded. Sample analysis is highlighted below:
The outcome of the mapping will help in identifying the systems which are not dependant on the others, and hence theoretically can be upgraded on a separate track independently.
SAP Upgrade Tools and Upgrade strategy
SAP Software Update Manager (SUM) is a multi-purpose tool, which supports following processes related with Upgrades:
The Software Update Manager checks the consistency of planned change and technical system where the change should be applied.
The current version of the Software Update Manager replaces well-known tools for SAP enhancement package implementation and upgrade
SUM Key Features Includes:
Deciding Upgrade strategy
The upgrade strategy is one of the main factors in determining how much downtime is involved. The SAP SUM tool offers following two update strategies :
Downtime minimization strategy using shadow instance technique of SAP’s Software Update Manager (SUM) tool is used to reduce the downtime during the Upgrade process. The Process overview report generated from SUM Tool during Test and Pre-Prod upgrades will also help in estimation of downtime required during the production upgrades.
Following are the major consideration of downtime minimization:
·
SAP SUM tool provides standard & advance options for Downtime Minimization based upon the shadow instance process:
Below depicted diagrams are showing the in-built features of SAP SUM tool on up-time and downtime period during the exection of
upgrade process using Standard and advance optiions of SUM tool.
SUM Standard Option for Downtime Minimization :
Below diagram discribes uptime and downtime processes in standard downtime minimization option of SUM tool.
SUM Advance Option for Extensive Downtime Minimization:
Below diagram discribes uptime and downtime processes in advance downtime minimization option of SUM tool.
Temporary increase of approx. 10%. in CPU & RAM and additional DB Storage of around 20-25% will be required for Shadow-technique to minimize downtime. However this needs to be analysed during the assessment/preparation phase of the project.
Hello Experts,
When we are trying to take backup using DB13, we got the following error. We are in a critical condition.
Please help.
Regards
Praveen
We are getting error during EHP 7 Upgrade,
We have followed the NOTE : 1622837 - Secure connection of AS ABAP to Oracle via SSFS and 1639578 - SSFS as password storage for primary database connect
During SUM earlier phase we have already configured SSFS and set the profile and environment variables.
usr\sap\<SID>\SYS\global\security\rsecssfs\data
usr\sap\<SID>\SYS\global\security\rsecssfs\key
default profile set to
rsec/ssfs_datapath $(DIR_GLOBAL)$(DIR_SEP)security$(DIR_SEP)rsecssfs$(DIR_SEP)data
rsec/ssfs_keypath $(DIR_GLOBAL)$(DIR_SEP)security$(DIR_SEP)rsecssfs$(DIR_SEP)key
env set to
setenv RSEC_SSFS_DATAPATH <drive>:\usr\sap\<SID>\SYS\global\security\rsecssfs\data
setenv RSEC_SSFS_KEYPATH <drive>:\usr\sap\<SID>\SYS\global\security\rsecssfs\key
Profile parameter : rsdb/ssfs_connect = 1
Environment variable: rsdb_ssfs_connect 1
This is all done and continued the and now reached PREPROCESSING stage where it got stopped again with same error for shadow system.
As per the above note , I believe we need to change only these ,
DB_CONNECT/SHADOW_DB_USER
DB_CONNECT/SHADOW_DB_PASSWORD
rsecssfx put DB_CONNECT/SHADOW_DB_USER SAPSR3SHD –plain
rsecssfx put DB_CONNECT/SHADOW_DB_PASSWORD xxx
And new shadow instance default profile need to be set values same values as above,
rsec/ssfs_datapath $(DIR_GLOBAL)$(DIR_SEP)security$(DIR_SEP)rsecssfs$(DIR_SEP)data
rsec/ssfs_keypath $(DIR_GLOBAL)$(DIR_SEP)security$(DIR_SEP)rsecssfs$(DIR_SEP)key
Then restarted Oracle and continued the SUM upgrade, but getting same error again.
Did I missed any steps for shadow systems ?
Moderator: <Logs moved to attachments>
Please help.
Thank you
Regards,
Raghu
Hi Experts,
I having below error message on step MAIN_INT/TOOLVERSXML_UPG(preprocessing) when I use SUM SP12 to do patching on ECC6.0 SP05 to SP16.
My OS is MS Server 2003 r2 and MSSQL2005.
1EETQ399 Last error code set is: Fatal Error: Mismatch between the last tool version run and the current one: Release in kernel type cur was 700, now in sys it changes to 720. 1EETQ204 Upgrade phase "TOOLVERSXML_UPG" aborted with severe errors ("20141224202041")
I have confirmed that kernel in ../usr/sap/DEV/SYS/exe is equal to ..\usr\sap\DEV\DVEBMGS02\exe and also in ..\usr\sap\SUM\abap\exe.
Also, the kernel showing in system is 720 when I checked via sapgui.
Please advise if you have any idea.
Thank you.
Por
Dear Experts,
We have Not Used and Activated IDOCS and ALE in our Environment upto Now. I have seen some Blogs which tells me how to Process and Work on IDoc's & ALE. But it doesn't not Mentions How to Start Activating them Initially In environment. Please suggest me some Helpful information how to Activate them in SAP ERP Business Suite.
Thanks, Regards,
Harsha.
After upgrade to EHP6, every time we set debug mode on with /h in command line, the first stop is in this FM: HOOK_DYNP_RAL_PAI.
This occurs on every transaction.
Any hint what could be this?
Regards,
Frisoni
Hi Guys
We are planning an EHP Upgrade from ERP 6.0 EHP4 to ERP 6.0 EHP6/7 (still deciding which one). Our goal is to perform this upgrade using Combined Upgrade & Unicode Conversion (CU&UC) as described in note 928729
When accesing note its says document is not released, anyone is experiencing the same issue?
https://websmp102.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=928729
Is this scenario possible or only when source release is lower than 7.0? My previous experience was 4.7X200 to SAP ERP6 EHP6
Can we combine upgrade/unicode conversion from NW 7.01 to NW 7.31/NW 7.4?
Any ideas welcomed!
Thanks!
hi
Dear all,
i am having sap erp 6.0 ehp4
i am going to upgrade my patch of basis from 106 to 116
abap 106 to 117
while applying patch i am getting warning in import log so please could anyone help me out for solving this warning
3WETW109 table "STC_SCN_HDR" does not exist in nametab.
3WETW109 table "STC_SCN_HDR_T" does not exist in nametab.
3WETW109 table "STC_SCN_TASKS" does not exist in nametab.
3WETW109 table "STC_CUST_PHASE" does not exist in nametab.
3WETW109 table "STC_CUST_PHASET" does not exist in nametab.
i am getting this type of warning in every basis patch
Azhar
Hi all,
I am busy upgrading my ECC6 Ehp 4 system to Ehp 6 SP13 and as past of the upgrade I included the SPAU transport as normal.
However this SPAU transport has the same object in 2 different tasks and the SUM tool via SAPup has a problem with this transport.
The phase MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_INC fail with the error:
FATAL ERROR: Duplicate object LIMU FUNC 'FRE_ORD_IN_CREATE_DOC' in transport
Is there a way in which I can force the upgrade to us this file or skip it, I can then apply it afterwards manually or get the DEV team to create a new transport.
I tried to add the file to the OPTIMPIGNORE.LST file but it did not help
Thanks
Henco
hi,
i am getting the below error in R/3 Upgrade:
UPGRADE/SWITCH: START OF PHASE LOADCRE_TMP
CURRENTPHASE MAIN_SWITCH/LOADCRE_TMP
...started at 20110211153653
Using phase log file 'LOADCRT.LOG'.
Reading Parameter File "D:\usr\sap\XLM\upg\abap\bin\LOAD.PKS" at 20110211153653
Reading Parameter File "D:\usr\sap\XLM\upg\abap\bin\LOADCTSK.LLT" at 20110211153659
Reading Parameter File "D:\usr\sap\XLM\upg\abap\bin\LOADCTSK.LLT" at 20110211153701
..finished at 20110211153701 with status 1 ERRORS OCCURED.
Error message set: 'Cannot open 'D:\usr\sap\XLM\upg\abap\bin\LOADARCH.SEL': The system cannot find the file specified.
in LOADCR:ELG I find
>>LOADCRE ERROR:, log file "EX000020.TPR": only 0 times "R3load.exe: job completed" found.
Analyze the log file EX000020.TPR for error messages or program abort.
in EX000020.TPR there is
D:\usr\sap\XLM\upg\abap\exe\R3load.exe: START OF LOG: 20110211153701
D:\usr\sap\XLM\upg\abap\exe\R3load.exe: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
D:\usr\sap\XLM\upg\abap\exe\R3load.exe: version R7.01/V1.4
Compiled Oct 31 2010 23:07:17
D:\usr\sap\XLM\upg\abap\exe\R3load.exe -tds err -ctf I D:\usr\sap\XLM\upg\abap\exchange\ctlpack\EX000020.CTL D:\usr\sap\XLM\upg\abap\exchange\tplpack\DDLORA.TPL D:\usr\sap\XLM\upg\abap\exchange\ctlpack\EX000020.TSK ORA -l D:\usr\sap\XLM\upg\abap\log\EX000020.TPR
(IDL) Info: ddldb2lib version is 701.23
(RLL) Info: reading db2 location lists from D:\usr\sap\XLM\upg\abap\exchange\tplpack\DDLORA.TPL
(RTF) ERROR: Traceflag expected in DB dependent control file "D:\usr\sap\XLM\upg\abap\exchange\tplpack\DDLORA.TPL" at line 4
D:\usr\sap\XLM\upg\abap\exe\R3load.exe: job finished with 1 error(s)
D:\usr\sap\XLM\upg\abap\exe\R3load.exe: END OF LOG: 20110211153701
Hi all,
We have created an Custom tcode and mapped it in Su24 With Object S_TCode with Check Indicator as Yes and Proposal NO. Now we want to delete this mapping from SU24. we are unable to do it.
When we execute SU24 and select Tcode, in Change Mode and click on Remove authorization object, it asks for TR. when we save the TR then again the object comes back with same mapping. We checked the program and S_Tcode is no where mapped.
Is there something that we are missing.
Thanks
Mohammed Wasim
Hi
We are Upgrading 4.7 EXT200 to ECC6.0 Include EHP4 SR1.
Due to XML file i have rest the Upgrade at Configuration phase.
Again started with SAPUP and At Extraction phase i have encontered the following error,
SEVERE ERROR: EA-APPL is in an undefined state,
that is not safe to be upgraded !!!
Reason: Upgrade wasn't completed.
Call the SAP Support!!!
Log:
399 "SAP_HRCSG","600","20090925","102915","20090925","102915","I","A","","","","",""
3 ETQ399 "SAP_HRCTH","600","20090925","102915","20090925","102915","I","A","","","","",""
3 ETQ399 "SAP_HRCTW","600","20090925","102915","20090925","102915","I","A","","","","",""
3 ETQ399 "SAP_HRCUS","600","20090925","102915","20090925","102915","I","A","","","","",""
3 ETQ399 "SAP_HRCVE","600","20090925","102915","20090925","102915","I","A","","","","",""
3 ETQ399 "SAP_HRCZA","600","20090925","102915","20090925","102915","I","A","","","","",""
3 ETQ399 "SAP_HRGXX","600","20090925","102915","20090925","102915","I","A","","","","",""
3 ETQ399 "SAP_HRRXX","600","20090925","102915","20090925","102915","I","A","","","","",""
3 ETQ399 "SEM-BW","600","20090925","102915","20090925","102915","I","A","","","","",""
3 ETQ399 "ST-PI","2008_1_700","20090925","102915","20090925","102915","I","A","","2005_1_620","","",""
3 ETQ399 "WEBCUIF","700","20090925","102915","20090925","102915","I","A","","","","",""
1AETQ228 Detected invalid (temporary) start release "EA-APPL
Please
Thanks
Anil
Hi,
We want to activate the Industry Extention Public Sector on SFW5, but prompted us with an error message that says we need to upgrade IS-PS-CA component on our ERP System from 600 to 617. Our ERP system has IS-PS-C on Release 600.
I would like to ask if how can we do the upgrade for the IS-PS-CA component in paticular? We have tried on SolMan but the target component release still shows to be 600 and not 617. We noticed that there is no Enhancement Package Installation option in the MOPZ calculation on SolMan, where the 617 release of IS-PS-CA must be displayed in the target constellation afterwards:
Appreciate your feedback on this.
Thanks!
Charles
EHP UPGRADE
PLANNING OF EHP UPGRADE
ASAP ROADMAP
The ASAP Roadmap provides the methodology for implementing and continuously optimizing your SAP System. ASAP Methodology for Implementation is the SAP roadmap for implementing SAP solutions in a cost-effective, speedy manner.
Standard ASAP 8 Methodology Phases-The Standard ASAP 8 Methodology is structured into the following phases.
Need of phases
These phases are the main milestones for your SAP System implementation project. Each phase has:
•Work packages, which consist of activities, for which project teams are responsible.
•Activities, which consist of tasks, which are processed by one or more team members.
•Tasks, which are carried out by a project team member. You can also access the How-to sections and accelerators at this level.
What is an SAP EHP Upgrade?
It's the installation of a new SAP ERP software version, together with the accumulation of all the relevant fixes in the form of a Support Package Stack.
Upgrade Tools
•PANAYA
•SUM
•solution browser
•SAPUp – SAP Upgrade
•SAPEhpi - SAP enhancement package installer
•SUM – Software Update Manager
SUM
Traditionally for applying SPS we use SPAM for ABAP & JSPM for Java
Some of the benefits of using SUM tool over these tools among others are
•Two different tools are not required to apply SPS. One SUM tool is used.
•No need to uncar the SAR files.
•Minimum downtime (Single downtime for both ABAP & Java combined).
•Simultaneously the SPS are applied to both the stacks.
Note:
Before you start the SUM tool do ensure that
•Latest Kernel is applied to the Source System
•Latest SPAM patch is applied.
Clone Mode: The Software Update Manager checks the tables in the database which will be cloned to the shadow system later on during the update. Here a shadow instance will be created with tables copied from source system.
Next input screens will ask for SPAM update. The SPAM was already updated; we choose to ignore the SPAM update. As in case of other tools such as SAPup & EHPI tool, SUM tool will also prompt for any missing notes that should be applied
SUM STEPS:
0. Administrator user and pass
1. Welcome:
2. Specify credential:
3. Select target:
4. Conform target:
5. Execute process:
5.1 Initialization
5.2 Extraction
5.3 Configuration
5.4 Check
5.5 Preprocessing
5.6 Execution
5.7 Post processing
5.8 Finalization
6. Summary:
PRE STEPS:
STEPS:
1. cd /sapcd/XXX702SPS08
3. SAPCAR -xvf SUM10SP08_1-20006543.SAR -R /usr/sap/xxx
4. Change ownership to sidadm:sapsys on /usr/sap/XXX/SUM
5. Change permission to 777 on /usr/sap/XXX/SUM
Do not use the '@' character in your database passwords, as the Software Update Manager cannot handle the passwords then.
Alter system set open_cursors = 20000 scope=both;
brconnect -u / -c -f stats -t oradict_stats
brconnect -u / -c -f stats -t system_stats
brconnect -c -u / -f stats -t all -f collect -p 4
Note:
Oradict_stats: Collects statistics for Oracle dictionary objects using DBMS_STATS package. For more information, see SAP Note 863811.
system_stats: Collects system (CPU, I/O) statistics using the DBMS_STATS package. For more information, see SAP Note 601395
brconnect -u / -c -f stats -t all -m +I -s P1 -f allsel, collect, method, precision -p 4
UPGRADE:
STEPS:
1. cd /UPGRADE/SUM/SUM/
2. ./STARTUP (It Will Start SL Controller)
3. Run SUM GUI
5. CD /UPGRADE/SUM/SUM/SDT/EXE
6. ./DSUgui
OR from Browser
4. http://<host name>:4239
SUM STEPS:
0. It will ask for Administrator user and pass we can give any user name and pass but this person will be responsible for whole upgrade. The role should be Administrator.
1. Welcome: In this phase we generally get the information of Detected SAP NetWeaver System. Like System technology: ABAP SYSTEM id: KUN, System Directory: /usr/sap/KUN It also recommended Reading note 1790828
2. Specify credential: this Part Used to ask about SIDADM Password so Provide KUNADM as user and password as *******
3. Select target: This part having two options one for Stack.xml file and manually prepared directory. We choose the location of Stack.XML File with XML name. EX-/usr/sap/KUN/ECCEHP6/SMSDXML_KUN_20130816212838.269.xml
4. Conform target: target release is confirmed here it will show current version and ehp of system and the target version of the system where we are going also it will say to enter a keyword from a snote mention in the screen.
5. Execute process
5.1Initialization:
5.2 Extraction:Once you click next to go to Extraction Phase, it will ask for DDIC user Password and also Database user SYSTEM password. The Extraction phase will extract the relevant files from the download directory.
Next input screens will ask for SPAM update. The SPAM was already updated; we choose to ignore the SPAM update. As in case of other tools such as SAPup & EHPI tool, SUM tool will also prompt for any missing notes that should be applied.
ERROR!!
Solution:
You’ll need to manually exchange R3trans & TP from /sapcd/sapcd/KUNUpgrade2013/KernelDuringKUNUpgrade***cp R3trans tp /usr/sap/KUN/SUM/abap/exe
Restart SUM step
5.3 5.3 Configuration: Here we mainly choose standard option and don’t check the check boxes about archiving and expert mode. Here it will ask number of Processes during up time and during down time like Batch, DDL, R3Trans etc. Usually we keep default Value. After 2 Hours we will get another screen which will ask for Addons. The Java configuration steps also starts. With SUM tool you can choose to automatically update the additional dialog instances if any. In older times we had to manually uninstall and install dialog instances
5.4 Check: It will check for the Spaces in database. If space is not available then create Tablespace for space
Solution:
create tablespace PSAPSR3731 extent management local autoallocate segment space management auto datafile '/oracle/XXX/sapdata2/xx3731_1/xx3731.data1' size 10000M autoextend off, '/oracle/XXX/sapdata2/xx3731_2/xx3731.data2' size 10000M autoextend off, '/oracle/XXX/sapdata2/xx3731_3/xx3731.data3' size 10000M autoextend off, '/oracle/XXX/sapdata2/xx3731_4/xx3731.data4' size 10000M autoextend off, '/oracle/XXX/sapdata2/xx3731_5/xx3731.data5' size 10000M autoextend off
OR Send an email to the DB2 Team to add the space
5.5 Preprocessing:In this phase SUM prepare the system for Upgrade.
Here we will have to move the SPDD TR#DR2K900020 into shadow system
Make sure the data & cofiles are available in /upgrade/SUM/SUM/abap/cofiles & /upgrade/SUM/SUM/abap/data with correct owner ship & permissions
Login to KUN shadow system with DDIC/000 client and create an dummy user (abapddic is created) user with su01 with an copy from DDIC
Goto SE06 ->System change option and check if it is modifiable
Import the SPDD TR into shadow system
Execute SE38-> UPGACTKORR
Give the SPDD TR(DR2K900020) in the Request name and execute. This will activate the request in the shadow system
Later on confirm with the Abap Team on SPDD TR and proceed further with the upgrade once everything is fine.
Error– “SQL10003C There are not enough system resources to process the request. The request cannot be processed. SQLSTATE=57011”.
Solution– Sent mail to DB2 DBA Team to increase the database buffer.
Possible Error:Batch job RSVBCHCK Failed with error code 8
SM13: Repeat or Delete all update records
1873772 - Last error code set: Single errors (code <= 8) found in logfile 'PSVBCHCK.ELG'
Transaction LBWQ; Delete all queues;
Transaction LBWG; Delete 06/13
5.6 Execution: In this phase SUM perform actual update in the system and downtime begin this phase take a long time.
Error occurred during the XPRAS execution
Solution– Continued by selecting Accept on “Accept non-severe errors and repeat phase MAIN_NEWBAS/XPRAS_AIMMRG”.
Other Solution:
This is due to multiple active BADI implementations. READ 1835882 - Error in XPRAS_AIMMRG phase during EHP installation for BADI Multiple active implementations
Steps to recover:
When finish, repeat the phase
Possible Error: Calling usr/sap/XXX/DVEBMG/tp failed with return code 8.
Solution: Note 912369 - FINB_TR_DEST, after import failures, transport errors
Transaction: /nFINB_TR_DEST at client 000
Create RFC FINBTR@XXXCLNT001 and FINBTR@XXCLNT300; Under RFC, input client with DDIC user/pwd.
1 .In the next Screen it will ask u to take Backup of ur database if you already done click action completed and hit Next.
2. End of downtime notification
5.7 Post processing:
In this phase system will unlock and downtime finished. In this phase some manual action required some of them are
1. we can reschedule the periodic job which has been DE schedule during downtime.to reschedule these job we can run a report BTSTRNS2 using DDIC user in transaction SE38.
2. Application specific post upgrade activity. Start ASU toolbox using transaction /ASU/UPGRADE
3. see the log of SUM from usr/sap/XXX/SUM/ABAP/log/LONGPOST.LOG and from message class and message number we and applied the relevant Snote.
5.8 Finalization
6. Summary: This phase will give the target version which completed and total time and system downtime.
POST UPGRADE
1. Implement note 1720495 before you start transaction SPAU (Note 1790828); Manual step is not needed.
Make sure to implement SAP note 1720495 immediately after a Support Package import, an enhancement package installation, or an upgrade and before making any adjustments in transaction SPAU
2. If you have SAP Kernel 7.10 or higher:
Execute the following commands:
cd <update directory>/abap/exe
./oraroot.sh <SAPSID>
If you have an MCOD system and/or the database name does not correspond to the SAP system name, use the following command to run oraroot.sh:
./oraroot.sh <SAPSID> <DBSID>
If you have one kernel directory: cd /usr/sap/<SAPSID>/SYS/exe/run
If you have two kernel directories: cd /sapmnt/<sapsid>/exe/(n)uc/<platform>
cp -p ./icmbnd.new ./icmbnd
chown root:sapsys icmbnd
chmod 4750 icmbnd
exit
cd $ORACLE_HOME/dbs
cp /usr/sap/<SAPSID>/SYS/exe/run/sapdba_role.sql sapdba_role.sql
sqlplus /nolog @sapdba_role.sql SR3
3. Call transaction STMS and choose OverviewSystems.
Double-click the system that has been upgraded and switch to the Change mode.
Do not change anything unless another action requires changes, and choose Save. Go back to the system overview.
4. Checking for Unused Indexes
Call transaction DB02.
Choose Missing Tables/Indexes.
Choose Unknown objects in ABAP Dictionary.
Check if there are unused indexes in the database. If this is the case, delete them manually.
For more information, see SAP Note 1227270
5. Oracle: Deleting Tablespaces
Select table_name, tablespace_name from dba_tables where TABLESPACE_NAME='PSAPSR3702';
Select index_name from dba_indexes where tablespace_name='PSAPSR3702';
Note 1819182 - Tables (TTREE*) remain in old exchange tablespace
In transaction SE13 or SE11, change the data type SSEXC to APPL0 for the tables and activate your data. After you do this, you can use
a) SE14
b) ICNV
c) DB tools
to move the table to a different tablespace (for TABART APPL0).
SE11-> Technical Setting -> change data class from SSEXC to APPL0
Check TAORA for APP0
1. Call transaction ICNV and read the online documentation ("I" button"). Converting a table using ICNV is a complex procedure during which, for example, changes to the table contents are made using a database trigger. It is important that you have a basic understanding of how the transaction works.
2. Call transaction SE14, enter the name of the table that you want to move and select "Edit" and then "Storage Parameters".
3. Select "For new creation" and use the "current database parameters" as a template (if required). Switch to "Change" mode.
4. After "TABLESPACE" and "INDEXSPACE", enter the new tablespaces required for the tables or index data.(Change PSAPSR3702 to PSAPSR3)
5. Save your entries.
6. Call transaction ICNV.
7. Select "Edit->Add table" and enter the name of the table that you want to move. Do not change the proposed scenario.
8. Follow the steps proposed by the wizard (choose "Assistant" or perform the following steps manually using the "Control" menu).
a) Initialization
b) Data transfer
c) Transfer
d) Delete entry
Shutdown Oracle;
brspace –f tsdrop
brspace -c force -o process, time -u / -f tbreorg -a reorg -tablespace PSAPSR3702 -t "*" -parallel 3 -degree 3 -newts PSAPSR3
Problem:
ZPPSFIF004
But when I was trying to upload a file from application server to table using a z program found the below error.
Solution:
Fix RFC WEBMETHOD.
#1859173 - Taking into account of external services in SU25, improved display in step 2b
#1850378 - Handling of (historically created) defective modification flags in SU24 data by SU25
#1878702 - Optimizing the navigation in step 2b and the transport connection
As root, run ./saproot.sh SID in /sapmnt/SID/exe
Rename folder /oracle/netbackup_script.bak to netbackup_script.bak
Create link for netbackup
IMPORTANT QUESTION:
Q. How we will know that shadow instance has been created in preprocessing Phase?
A. Pf – ef | grep shd Note: Shadow instance will +1 more than instance, 00 will 01
Q. There is a report we need to run in preprocessing Phase during SPAU/SPAD?
A. UPGACTKORR Its Activate Request in Shadow System.
Q. How to unlock shadow system and why we use it?
A. usr/sap/sid/upg/abap/bin
./sapup unlockSHD SSH
Q. How many Minimum Background work processes needed in EHP Upgrade?
A. 4
Q. What used to happen during Downtime?
A. 1. Kernel Switch from old kernel to new kernel
2. Table conversion
3. User will not able to login
Q. What is /ASU/upgrade?
ASU Toolbox
Q. Reset Administrator password of SUM.
We have a requirement to validate the entered services while creating PR thru ME51N as services must belong to the entered Material Group.For that I have tried the BADI ME_PROCESS_req_cust and Customer Exit EXIT_SAPLMEREQ_005 but not able to find solution. Tried to access the service table ESLL by using class if_services_mm~get_srv_data but not able to do it. Please help us in this regard.
Hi Experts ,
I am upgrading ECC 6 EHP 6 from Stack 5 to Stack 12 upgrading with SUM 1.0.11.5
Upgrade at Execution stopped at MAIN_SWITCH/SUBMOD_SWITCH_OLDREL/JOB_RSVBCHCK_D as shown below ,
I guess I have to log in the system and delete/process these from extraction queue , please let me know the process to do this
trc file: "dev_disp", trc level: 1, release: "700"
---------------------------------------------------
sysno 00
sid NSR
systemid 562 (PC with Windows NT)
relno 7000
patchlevel 0
patchno 144
intno 20050900
make: multithreaded, Unicode, 64 bit, optimized
pid 2008
Sat Jan 16 20:31:01 2016
kernel runs with dp version 232000(ext=109000) (@(#) DPLIB-INT-VERSION-232000-UC)
length of sys_adm_ext is 576 bytes
*** SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (00 2008) [dpxxdisp.c 1243]
shared lib "dw_xml.dll" version 144 successfully loaded
shared lib "dw_xtc.dll" version 144 successfully loaded
shared lib "dw_stl.dll" version 144 successfully loaded
shared lib "dw_gui.dll" version 144 successfully loaded
shared lib "dw_mdm.dll" version 144 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3900
Sat Jan 16 20:31:06 2016
*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5371]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: start server >NSAP_NSR_00 <
DpShMCreate: sizeof(wp_adm) 19248 (1480)
DpShMCreate: sizeof(tm_adm) 5652128 (28120)
DpShMCreate: sizeof(wp_ca_adm) 24000 (80)
DpShMCreate: sizeof(appc_ca_adm) 8000 (80)
DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552064/552080
DpShMCreate: sizeof(comm_adm) 552080 (1088)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm) 0 (104)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm) 0 (72)
DpShMCreate: sizeof(vmc_adm) 0 (1864)
DpShMCreate: sizeof(wall_adm) (41664/36752/64/192)
DpShMCreate: sizeof(gw_adm) 48
DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000DA30050, size: 6342672)
DpShMCreate: allocated sys_adm at 000000000DA30050
DpShMCreate: allocated wp_adm at 000000000DA32150
DpShMCreate: allocated tm_adm_list at 000000000DA36C80
DpShMCreate: allocated tm_adm at 000000000DA36CE0
DpShMCreate: allocated wp_ca_adm at 000000000DF9AB80
DpShMCreate: allocated appc_ca_adm at 000000000DFA0940
DpShMCreate: allocated comm_adm at 000000000DFA2880
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 000000000E029510
DpShMCreate: allocated gw_adm at 000000000E029590
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 000000000E0295C0
DpShMCreate: allocated wall_adm at 000000000E0295D0
MBUF state OFF
DpCommInitTable: init table for 500 entries
ThTaskStatus: rdisp/reset_online_during_debug 0
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 4096 kByte.
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
<ES> 127 blocks reserved for free list.
ES initialized.
Sat Jan 16 20:31:07 2016
J2EE server info
start = TRUE
state = STARTED
pid = 3216
argv[0] = D:\usr\sap\NSR\DVEBMGS00\exe\jcontrol.EXE
argv[1] = D:\usr\sap\NSR\DVEBMGS00\exe\jcontrol.EXE
argv[2] = pf=D:\usr\sap\NSR\SYS\profile\NSR_DVEBMGS00_NSAP
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=65000
argv[5] = -DSAPSYSTEM=00
argv[6] = -DSAPSYSTEMNAME=NSR
argv[7] = -DSAPMYNAME=NSAP_NSR_00
argv[8] = -DSAPPROFILE=D:\usr\sap\NSR\SYS\profile\NSR_DVEBMGS00_NSAP
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1633]
***LOG Q0K=> DpMsAttach, mscon ( NSAP) [dpxxdisp.c 11822]
DpStartStopMsg: send start message (myname is >NSAP_NSR_00 <)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: Initalizing shared memory of size 60000000 for monitoring segment.
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1050]
DpMsgAdmin: Set patchno for this platform to 144
Release check o.K.
DpJ2eeLogin: j2ee state = CONNECTED
Sat Jan 16 20:31:09 2016
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 4 / sock 956
(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:58742) [nixxi.cpp 4424]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=3216)
*** ERROR => DpProcKill: kill failed [dpntdisp.c 371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Sat Jan 16 20:31:47 2016
*** ERROR => DpHdlDeadWp: W0 (pid 2736) died [dpxxdisp.c 14532]
*** ERROR => DpHdlDeadWp: W1 (pid 3508) died [dpxxdisp.c 14532]
*** ERROR => DpHdlDeadWp: W2 (pid 3024) died [dpxxdisp.c 14532]
*** ERROR => DpHdlDeadWp: W3 (pid 4012) died [dpxxdisp.c 14532]
*** ERROR => DpHdlDeadWp: W4 (pid 3968) died [dpxxdisp.c 14532]
*** ERROR => DpHdlDeadWp: W5 (pid 2912) died [dpxxdisp.c 14532]
my types changed after wp death/restart 0xbf --> 0xbe
*** ERROR => DpHdlDeadWp: W6 (pid 3672) died [dpxxdisp.c 14532]
my types changed after wp death/restart 0xbe --> 0xbc
*** ERROR => DpHdlDeadWp: W7 (pid 1344) died [dpxxdisp.c 14532]
my types changed after wp death/restart 0xbc --> 0xb8
*** ERROR => DpHdlDeadWp: W8 (pid 2640) died [dpxxdisp.c 14532]
*** ERROR => DpHdlDeadWp: W9 (pid 3536) died [dpxxdisp.c 14532]
*** ERROR => DpHdlDeadWp: W10 (pid 3608) died [dpxxdisp.c 14532]
my types changed after wp death/restart 0xb8 --> 0xb0
*** ERROR => DpHdlDeadWp: W11 (pid 3424) died [dpxxdisp.c 14532]
my types changed after wp death/restart 0xb0 --> 0xa0
*** ERROR => DpHdlDeadWp: W12 (pid 2928) died [dpxxdisp.c 14532]
my types changed after wp death/restart 0xa0 --> 0x80
*** DP_FATAL_ERROR => DpWPCheck: no more work processes
*** DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
NiWait: sleep (10000ms) ...
NiISelect: timeout 10000ms
NiISelect: maximum fd=993
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Sat Jan 16 20:31:57 2016
NiISelect: TIMEOUT occured (10000ms)
dump system status
Workprocess Table (long) Sun Jan 17 04:31:57 2016
========================
No Ty. Pid Status Cause Start Err Sem CPU Time Program Cl User Action Table
-------------------------------------------------------------------------------------------------------------------------------
0 DIA 2736 Ended no 1 0 0
1 DIA 3508 Ended no 1 0 0
2 DIA 3024 Ended no 1 0 0
3 DIA 4012 Ended no 1 0 0
4 DIA 3968 Ended no 1 0 0
5 DIA 2912 Ended no 1 0 0
6 UPD 3672 Ended no 1 0 0
7 ENQ 1344 Ended no 1 0 0
8 BTC 2640 Ended no 1 0 0
9 BTC 3536 Ended no 1 0 0
10 BTC 3608 Ended no 1 0 0
11 SPO 3424 Ended no 1 0 0
12 UP2 2928 Ended no 1 0 0
Dispatcher Queue Statistics Sun Jan 17 04:31:57 2016
===========================
+------+--------+--------+--------+--------+--------+
| Typ | now | high | max | writes | reads |
+------+--------+--------+--------+--------+--------+
| NOWP | 0 | 2 | 2000 | 5 | 5 |
+------+--------+--------+--------+--------+--------+
| DIA | 5 | 5 | 2000 | 5 | 0 |
+------+--------+--------+--------+--------+--------+
| UPD | 0 | 0 | 2000 | 0 | 0 |
+------+--------+--------+--------+--------+--------+
| ENQ | 0 | 0 | 2000 | 0 | 0 |
+------+--------+--------+--------+--------+--------+
| BTC | 0 | 0 | 2000 | 0 | 0 |
+------+--------+--------+--------+--------+--------+
| SPO | 0 | 0 | 2000 | 0 | 0 |
+------+--------+--------+--------+--------+--------+
| UP2 | 0 | 0 | 2000 | 0 | 0 |
+------+--------+--------+--------+--------+--------+
max_rq_id 12
wake_evt_udp_now 0
wake events total 8, udp 6 ( 75%), shm 2 ( 25%)
since last update total 8, udp 6 ( 75%), shm 2 ( 25%)
Dump of tm_adm structure: Sun Jan 17 04:31:57 2016
=========================
Term uid man user term lastop mod wp ta a/i (modes)
Workprocess Comm. Area Blocks Sun Jan 17 04:31:57 2016
=============================
Slots: 300, Used: 1, Max: 0
+------+--------------+----------+-------------+
| id | owner | pid | eyecatcher |
+------+--------------+----------+-------------+
| 0 | DISPATCHER | -1 | *WPCAAD000* |
NiWait: sleep (5000ms) ...
NiISelect: timeout 5000ms
NiISelect: maximum fd=993
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Sat Jan 16 20:32:02 2016
NiISelect: TIMEOUT occured (5000ms)
DpHalt: shutdown server >NSAP_NSR_00 < (normal)
DpJ2eeDisableRestart
DpModState: buffer in state MBUF_PREPARED
NiBufSend starting
NiIWrite: hdl 3 sent data (wrt=110,pac=1,MESG_IO)
MsINiWrite: sent 110 bytes
MsIModState: change state to SHUTDOWN
DpModState: change server state from STARTING to SHUTDOWN
Switch off Shared memory profiling
ShmProtect( 57, 3 )
ShmProtect(SHM_PROFILE, SHM_PROT_RW
ShmProtect( 57, 1 )
ShmProtect(SHM_PROFILE, SHM_PROT_RD
DpWakeUpWps: wake up all wp's
Stop work processes
Stop gateway
killing process (3920) (SOFT_KILL)
Stop icman
killing process (2172) (SOFT_KILL)
Terminate gui connections
wait for end of work processes
wait for end of gateway
[DpProcDied] Process lives (PID:3920 HANDLE:712)
waiting for termination of gateway ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=993
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Sat Jan 16 20:32:03 2016
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process died (PID:3920 HANDLE:712)
wait for end of icman
[DpProcDied] Process lives (PID:2172 HANDLE:728)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=993
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Sat Jan 16 20:32:04 2016
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2172 HANDLE:728)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=993
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Sat Jan 16 20:32:05 2016
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2172 HANDLE:728)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=993
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Sat Jan 16 20:32:06 2016
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2172 HANDLE:728)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=993
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Sat Jan 16 20:32:07 2016
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2172 HANDLE:728)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=993
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Sat Jan 16 20:32:08 2016
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2172 HANDLE:728)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=993
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Sat Jan 16 20:32:09 2016
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2172 HANDLE:728)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=993
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Sat Jan 16 20:32:10 2016
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2172 HANDLE:728)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=993
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Sat Jan 16 20:32:11 2016
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2172 HANDLE:728)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=993
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Sat Jan 16 20:32:12 2016
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2172 HANDLE:728)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=993
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Sat Jan 16 20:32:13 2016
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process lives (PID:2172 HANDLE:728)
waiting for termination of icman ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=993
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Sat Jan 16 20:32:14 2016
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process died (PID:2172 HANDLE:728)
[DpProcDied] Process died (PID:3216 HANDLE:716)
DpStartStopMsg: send stop message (myname is >NSAP_NSR_00 <)
NiIMyHostName: hostname = 'NSAP'
AdGetSelfIdentRecord: > <
AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 4 (AD_STARTSTOP), ser 0, ex 0, errno 0
DpConvertRequest: net size = 189 bytes
NiBufSend starting
NiIWrite: hdl 3 sent data (wrt=562,pac=1,MESG_IO)
MsINiWrite: sent 562 bytes
send msg (len 110+452) to name -, type 4, key -
DpStartStopMsg: stop msg sent
NiIRead: hdl 3 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 3
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 3 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 3
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 3 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 3
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 3 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 3
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 3 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 3
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 3 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 3
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 3 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 3
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 3 recv would block (errno=EAGAIN)
NiIRead: read for hdl 3 timed out (0ms)
DpHalt: no more messages from the message server
DpHalt: send keepalive to synchronize with the message server
NiBufSend starting
NiIWrite: hdl 3 sent data (wrt=114,pac=1,MESG_IO)
MsINiWrite: sent 114 bytes
send msg (len 110+4) to name MSG_SERVER, type 0, key -
MsSndName: MS_NOOP ok
Send 4 bytes to MSG_SERVER
NiIRead: hdl 3 recv would block (errno=EAGAIN)
NiIPeek: peek successful for hdl 3 (r)
NiIRead: hdl 3 received data (rcd=114,pac=1,MESG_IO)
NiBufIIn: NIBUF len=114
NiBufIIn: packet complete for hdl 3
NiBufReceive starting
MsINiRead: received 114 bytes
MSG received, len 110+4, flag 3, from MSG_SERVER , typ 0, key -
Received 4 bytes from MSG_SERVER
Received opcode MS_NOOP from msg_server, reply MSOP_OK
MsOpReceive: ok
MsSendKeepalive : keepalive sent to message server
NiIRead: hdl 3 recv would block (errno=EAGAIN)
Sat Jan 16 20:32:15 2016
NiIPeek: peek for hdl 3 timed out (r; 1000ms)
NiIRead: read for hdl 3 timed out (1000ms)
DpHalt: no more messages from the message server
DpHalt: sync with message server o.k.
detach from message server
***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c 12168]
NiBufSend starting
NiIWrite: hdl 3 sent data (wrt=110,pac=1,MESG_IO)
MsINiWrite: sent 110 bytes
MsIDetach: send logout to msg_server
MsIDetach: call exit function
DpMsShutdownHook called
NiBufISelUpdate: new MODE -- (r-) for hdl 3 in set0
SiSelNSet: set events of sock 784 to: ---
NiBufISelRemove: remove hdl 3 from set0
SiSelNRemove: removed sock 784 (pos=3)
SiSelNRemove: removed sock 784
NiSelIRemove: removed hdl 3
MBUF state OFF
AdGetSelfIdentRecord: > <
AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
blks_in_queue/wp_ca_blk_no/wp_max_no = 1/300/13
LOCK WP ca_blk 1
make DISP owner of wp_ca_blk 1
DpRqPutIntoQueue: put request into queue (reqtype 1, prio LOW, rq_id 15)
MBUF component DOWN
NiICloseHandle: shutdown and close hdl 3 / sock 784
NiBufIClose: clear extension for hdl 3
MsIDetach: detach MS-system
cleanup EM
EsCleanup ....
EmCleanup() -> 0
Es2Cleanup: Cleanup ES2
***LOG Q05=> DpHalt, DPStop ( 2008) [dpxxdisp.c 10421]
Good Bye .....
Dear All,
We required a detail history report for the rights given to users.
eg. How many movement types are given ?
How many plant's rights are given to users etc..
Thanks
Dharmendra C. Gohel