Saturday, January 30, 2016

Graphical Form Painter could not be called (FORMPAINTER_CREATE_WINDOW, ) SAP GUI 7.4 Issue

During SE71 sap script editor
when opening Layout getting error message as below

    Graphical Form Painter could not be called (FORMPAINTER_CREATE_WINDOW, )

        Message no. TD245

    Diagnosis

        An error occurred structuring the graphical Form Painter.

    System Response

        The system switches to the alphanumeric Form Painter.
 


I have SAP GUI 7.40 Patch level 7 which causing this issue

To resolve issue followed below steps

1. Copy those files from installation DVD Dump
    i.e. E:\Software\GUI 7.4\50126622_6\BD_NW_7.0_Presentation_7.40_Comp._1_\PRES1\GUI\WINDOWS\WIN32\SapGui

    h5dlg32.dll, h5icon32.dll, h5krnl32.dll, h5menu32.dll, h5rtf32.dll, h5tool32.dll, saprtf.ocx
    into C:\Program Files (x86)\SAP\FrontEnd\SAPgui

2. Open command prompt with Run as Administrator
    change to directory C:\Windows\SysWOW64
    execute below command
    regsvr32 "C:\Program Files (x86)\SAP\FrontEnd\SAPgui\saprtf.ocx"
    will get Success message
    Close command prompt
    Close SAP GUI

    Open SAP GUI and check it will resolve issue.




Wednesday, January 06, 2016

Disp+work failed to start



Disp+work failed to start
on checking dev_disp log file i.e. E:\usr\sap\SOL\DVEBMGS00\work\dev_disp
getting details as below
Wed Jan 06 13:33:20 2016
*** Error 11 while initializing OS dependent part.
*** ERROR => DpEmInit: EmInit (1) [dpxxdisp.c   10781]
*** ERROR => DpMemInit: DpEmInit (-1) [dpxxdisp.c   10695]
*** DP_FATAL_ERROR => DpSapEnvInit: DpMemInit
*** DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
NiWait: sleep (10000ms) ...

Error 11 while initializing OS dependent part. - comes normally there are not enough space in mermory hence restart OS and started instance again which work fine.

Some times this happen in Windows OS due to memory release issue.












Monday, January 04, 2016

JAVA instance not starting up



When try to login to SAP PI JAVA stack getting below error message.

Restarted JAVA Instance but in management studio Jstart process not started and showing in yellow.

To troubleshoot I had checked dev_server0 log file ( i.e. E:\usr\sap\PIT\DVEBMGS00\work\dev_server0.log )

Which has below details.

concurrent-mark-sweep perm gen reserved 1048576K, committed 1048576K, used 58269K [0x000000017fff0000, 0x00000001bfff0000, 0x00000001bfff0000)
F 
F [Thr 5088] Mon Jan 04 15:30:30 2016
F  [Thr 5088] *** LOG => SfCJavaVm: exit hook is called. (rc = 2150)
F  
F  ********************************************************************************
F  *** ERROR => Java node 'server0' terminated with exit code 2150.
F  ***
F  *** Please see section 'Java program exit codes'
F  *** in SAP Note 1316652 for additional information and trouble shooting advice.
F  ********************************************************************************
F 
F  [Thr 5088] *** LOG => exiting (exitcode 2150, retcode 1).
M  [Thr 5088] CCMS: CCMS Monitoring Cleanup finished successfully.

To more troubleshoot require to check std_server0.log file ( i.e. E:\usr\sap\PIT\DVEBMGS00\work\std_server0.log )

Below error
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Initialization of destination UMEBackendConnection failed: Logon not possible (error in license check) on localhost sysnr 00
                at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:465)
                at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
                at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
                at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
                at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Initialization of destination UMEBackendConnection failed: Logon not possible (error in license check) on localhost sysnr 00
                at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:679)
                at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getNewInstance(PrincipalDatabagFactory.java:203)
                at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:153)
                at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:215)
                at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:139)
                at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:94)
                at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:211)
                at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:288)
                ... 7 more
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Initialization of destination UMEBackendConnection failed: Logon not possible (error in license check) on localhost sysnr 00
                at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:217)
                at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:501)
                at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:530)
                ... 14 more
Caused by: com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Initialization of destination UMEBackendConnection failed: Logon not possible (error in license check) on localhost sysnr 00

Based on above identified there is issue with SAP License key which require to apply.

Wednesday, December 30, 2015

Oracle 12c Architecture change

Hi All,

From busy schedule i got chance to get understanding.

From Oracle Database 12c Release 1, the concept of multitenant environment has been introduced. The multitenant architecture enables an Oracle database to function as a multitenant container database (CDB) that includes zero, one, or many customer-created pluggable databases (PDBs). A PDB is a portable collection of schemas, schema objects, and nonschema objects that appears to an Oracle Net client as a non-CDB. All Oracle databases prior to Oracle Database 12 were non-CDBs. 


A CDB includes the following components:

  • Root
    The root, named CDB$ROOT, stores Oracle-supplied metadata and common users. An example of metadata is the source code for Oracle-supplied PL/SQL packages. A common user is a database user known in every container. A CDB has exactly one root.
  • Seed
    The seed, named PDB$SEED, is a template that you can use to create new PDBs. You cannot add objects to or modify objects in the seed. A CDB has exactly one seed.
  • PDBs
    A PDB appears to users and applications as if it were a non-CDB. For example, a PDB can contain the data and code required to support a specific application. A PDB is fully backward compatible with Oracle Database releases before Oracle Database 12c.
Each of these components is called a container. Therefore, the root is a container, the seed is a container, and each PDB is a container. Each container has a unique container ID and name within a CDB.

Also from Oracle Database 12c Rel 2 oracle introduce Oracle Enterprise Manager Express instead of oracle enterprise manager (EM) we used earlier.

https://docs.oracle.com/database/121/UPGRD/deprecated.htm#UPGRD60005

 
Will discuss on both here.

1. How could i know installed oracle 12c database is CDB or Non-CDB ?
Login to database using SQL plus and execute below query.

select name,cdb,con_id from v$database;

If your database Non-CDB, will get result similar to below



If your database CDB, will get result similar to below





In CDB & non-CDB database instance details remains same.


SQL> select instance_name,status,con_id from v$instance;

INSTANCE_NAME    STATUS           CON_ID
---------------- ------------ ----------
orcl             OPEN                  0


But Oracle Oracle Enterprise Manager Express show CDB and PDB details differently.



Normally you login with SQLPlus default get authenticated in CDB

SQL> select dbms_xdb_config.gethttpsport() from dual;

DBMS_XDB_CONFIG.GETHTTPSPORT()
------------------------------
                          5500

SQL> select con_id,name,open_mode from v$pdbs;

    CON_ID NAME                           OPEN_MODE
---------- ------------------------------ ----------
         2 PDB$SEED                       READ ONLY
         3 PDBORCL                        MOUNTED

SQL> alter pluggable database pdborcl open;

Pluggable database altered.

SQL> select con_id,name,open_mode from v$pdbs;

    CON_ID NAME                           OPEN_MODE
---------- ------------------------------ ----------
         2 PDB$SEED                       READ ONLY
         3 PDBORCL                        READ WRITE

SQL> alter session set container=pdborcl;

Session altered.

SQL> select dbms_xdb_config.gethttpsport() from dual;

DBMS_XDB_CONFIG.GETHTTPSPORT()
------------------------------
                             0

SQL> exec dbms_xdb_config.sethttpsport(5501);

PL/SQL procedure successfully completed.

SQL>