Outstanding DB conversions found



Issue

-No SUM, na fase Extraction

Conversion Check

WARNING: Outstanding DB conversions found:
Entry
ENQU/UI5/E_REP 0CNVI 20140728DDIC


Remove all converter entries as described in the guide and repeat this phase. 

Solution

Solution indicated for SUM version SP11. For older versions consult the correct update guide, in section Cleaning Up Terminated Conversions in the DB Conversion Phases

1. Determine the objects that are affected.

1. Start the database utility transaction (transaction SE14) and choose DB Requests Mass Processing .

2. Choose All requests.
The worklist of the conversion program appears. This worklist was generated by developments or modifications in your SAP system, but has not yet been processed.


3. Choose DB requests Created with import .
The worklist that was not processed correctly during the last update appears.

2. Check the meaning and status of the requests.
In contrast to the procedure for the message Restart logs of DB conversions found, this procedure can also include requests for indexes, views and matchcode objects. The requests that are found are not always terminated. They might not even have been started.

1. Ask the last person who changed the object if the request should still be processed.

2. If the user does not want it to be processed, select the request and choose Delete selected.
This removes the objects from the worklist of the conversion program.
Do not remove requests from the last update.

3. Process the outstanding requests.
You can select the requests from the list of mass processing requests and schedule a job for execution with the
function Schedule selections.

1. Go to the detailed display of the object by double-clicking it in the list of requests created by the import.

2. Schedule the request, or continue it. Since you do not know how long this takes, choose processing type Background.


DTecno Consultoria SAP - Suporte SAP Remoto sob Demanda
Keywords: Consultoria SAP, Consultor SAP, SAP Remoto, SAP Basis, Suporte SAP Remoto

Referencia


Could not open the ICU common library



Problema 1 
SAPup> Starting subprocess with PID 9633946 in phase 'TOOLVERSION_UNI' at 20140730101422
    ENV: DIR_LIBRARY=/usr/sap/TST/DVEBMGS00/exe
    ENV: JAVA_HOME=/usr/java14_64
    ENV: LIBPATH=/usr/sap/TST/DVEBMGS00/exe:/usr/sap/TST/SUM/jvm/jre/lib/ppc64/server:/usr/sap/TST/SUM/jvm/jre/lib/ppc64:/usr/sap/TST/SU
M/jvm/jre/../lib/ppc64:/usr/sap/TST/SUM/jvm/jre/lib/ppc64/jli:/usr/sap/TST/SUM/jvm/jre/../lib/ppc64/jli:/usr/lib:/lib:/usr/sap/TST/SYS/e
xe/run:/oracle/client/11x_64/instantclient
    ENV: NLS_LANG=AMERICAN_AMERICA.UTF8
    ENV: ORACLE_BASE=/oracle
    ENV: ORACLE_HOME=/oracle/TST/112_64
    ENV: ORACLE_SID=TST
    ENV: PATH=/usr/sap/TST/DVEBMGS00/exe:/oracle/TST/112_64/bin:/usr/java14_64/bin:.:/home/tstadm:/usr/sap/TST/SYS/exe/run:/usr/bin:/etc
:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/java5/jre/bin:/usr/java5/bin
    ENV: SAPDATA_HOME=/oracle/TST
    ENV: SAPSYSTEMNAME=TST
    ENV: dbms_type=ORA
    ENV: dbs_ora_schema=SAPSR3
    ENV: dbs_ora_tnsname=TST

EXECUTING /usr/sap/TST/DVEBMGS00/exe/tp  -V
Could not open the ICU common library.
   The following files must be in the path described by
   the environment variable "LIBPATH":
   libicuuc40.a, libicudata40.a, libicui18n40.a [nlsui0.c 1548] pid = 9633946
LIBPATH is currently set to /usr/sap/TST/DVEBMGS00/exe:/usr/sap/TST/SUM/jvm/jre/lib/ppc64/server:/usr/sap/TST/SUM/jvm/jre/lib/ppc64:/usr
/sap/TST/SUM/jvm/jre/../lib/ppc64:/usr/sap/TST/SUM/jvm/jre/lib/ppc64/jli:/usr/sap/TST/SUM/jvm/jre/../lib/ppc64/jli:/usr/lib:/lib:/usr/sa
p/TST/SYS/exe/run:/oracle/client/11x_64/instantclient  [nlsui0.c 1551] pid = 9633946
SAPup> Process with PID 9633946 terminated with status 255 at 20140730101422!

Problema 2
SAPup> Starting subprocess with PID 12320986 in phase 'TOOLVERSION_UNI' at 20140730110321
    ENV: DIR_LIBRARY=/usr/sap/TST/DVEBMGS00/exe
    ENV: JAVA_HOME=/usr/java14_64
    ENV: LIBPATH=/usr/sap/TST/DVEBMGS00/exe:/usr/sap/TST/SUM/jvm/jre/lib/ppc64/server:/usr/sap/TST/SUM/jvm/jre/lib/ppc64:/usr/sap/TST/SU
M/jvm/jre/../lib/ppc64:/usr/sap/TST/SUM/jvm/jre/lib/ppc64/jli:/usr/sap/TST/SUM/jvm/jre/../lib/ppc64/jli:/usr/lib:/lib:/usr/sap/TST/SYS/e
xe/run:/oracle/client/11x_64/instantclient
    ENV: NLS_LANG=AMERICAN_AMERICA.UTF8
    ENV: ORACLE_BASE=/oracle
    ENV: ORACLE_HOME=/oracle/TST/112_64
    ENV: ORACLE_SID=TST
    ENV: PATH=/usr/sap/TST/DVEBMGS00/exe:/oracle/TST/112_64/bin:/usr/java14_64/bin:.:/home/tstadm:/usr/sap/TST/SYS/exe/run:/usr/bin:/etc
:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/java5/jre/bin:/usr/java5/bin
    ENV: SAPDATA_HOME=/oracle/TST
    ENV: SAPSYSTEMNAME=TST
    ENV: dbms_type=ORA
    ENV: dbs_ora_schema=SAPSR3
    ENV: dbs_ora_tnsname=TST

EXECUTING /usr/sap/TST/DVEBMGS00/exe/tp  -V
ERROR in child process: Cannot execute '/usr/sap/TST/DVEBMGS00/exe/tp': Exec format error

SAPup> Process with PID 12320986 terminated with status 27 at 20140730110321!

Solução
- Stopsap
- Com o usuário root logado, execute o comando.
> ps -ef | grep sapstartsrv

- Finalize o processo com o comando
kill -9 <sapstartsrv pid>

- Com o usuário <sid>adm, execute os comandos
sapcpe pf=/usr/sap/<sid>/SYS/profile/<SID>_DVEBMGS0_<hostname>
> sapcpe pf=/usr/sap/<sid>/SYS/profile/START_SCS<NR>_<hostname>

- Inicie o SAP

>startsap

DTecno Consultoria SAP - Suporte SAP Remoto sob Demanda
Keywords: Consultor SAP, SAP Remoto, SAP Basis, Suporte SAP Remoto

Referencia
http://vinbasis.wordpress.com/2012/10/10/sap-kernel-upgrade-700-to-720-on-unix-anix/

SUM - Stack.xml - Incorrect input; provide the correct path to the directory.


Problema 1

<!--LOGHEADER[START]/-->
<!--HELP[Manual modification of the header may cause parsing problem!]/-->
<!--LOGGINGVERSION[2.0.7.1006]/-->
<!--NAME[/usr/sap/SLM/<SID>/sdt/log/SUM/DEFINE-TARGET-SOURCE_07.LOG]/-->
<!--PATTERN[DEFINE-TARGET-SOURCE_07.LOG]/-->
<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%6s]: %m)]/-->
<!--ENCODING[UTF8]/-->
<!--LOGHEADER[END]/-->
Jul 21, 2014 11:10:27 AM [Info  ]: The detected system topology is DUAL_STACK
Jul 21, 2014 11:10:28 AM [Info  ]: Dialog eliminator inboxOpEliminator does not allow to omit dialog DefineTargetDialog
Jul 21, 2014 11:10:28 AM [Info  ]: Dialog eliminator stackOpEliminator does not allow to omit dialog DefineTargetDialog
Jul 21, 2014 11:10:28 AM [Info  ]: Dialog eliminator ContentLocationDialogEleiminator does not allow to omit dialog DefineTargetDialog
Jul 21, 2014 11:10:28 AM [Info  ]: Dialog eliminator DownloadSMPEliminator allows to omit dialog DefineTargetDialog
Jul 21, 2014 11:11:04 AM [Info  ]: Setting catalog key inbox.option to value true into shared input catalog.
Jul 21, 2014 11:11:04 AM [Info  ]: Setting catalog key stack.option to value false into shared input catalog.
Jul 21, 2014 11:11:05 AM [Error ]: The provided Stack file or Directory: /midias/stack.xml, is not valid.
Jul 21, 2014 11:11:05 AM [Info  ]: Dialog eliminator inboxOpEliminator does not allow to omit dialog DefineTargetDialog
Jul 21, 2014 11:11:05 AM [Info  ]: Dialog eliminator stackOpEliminator does not allow to omit dialog DefineTargetDialog
Jul 21, 2014 11:11:05 AM [Info  ]: Dialog eliminator ContentLocationDialogEleiminator does not allow to omit dialog DefineTargetDialog
Jul 21, 2014 11:11:05 AM [Info  ]: Dialog eliminator DownloadSMPEliminator allows to omit dialog DefineTargetDialog

Problema 2


- Incorrect input; provide the correct path to the directory.


Problema 3

 Some of the archives defined in the stack configuration file were not found in the download directory.

Solução

- Crie a MPOZ e faça o download do arquivo stack.xml
- Faça o download dos arquivos apontados na MPOZ via SAP Download Manager.
- Crie um diretório no servidor e deixe os arquivos baixados junto com o stack.xml.
- Inicie o SUM.
- Quando solicitado no step “Select Target System Version”, selecione o arquivo stack.xml no diretório criado e marque a opção Stack configuration file (XML).

DTecno Consultoria SAP - Suporte SAP Remoto sob Demanda
Keywords: Consultor SAP, SAP Remoto, SAP Basis, Suporte SAP Remoto