ORA-04023 during DBUA upgrade from Oracle 12.2.0.1 to Oracle 19c

During Oracle Upgrade using DBUA from 12 to 19, you got ORA-04023 - Object SYS.DBMS_STANDARD could not be validated or authorized.

There are some causes to this error :

ORACLE_PATH or SQLPATH are set in the user environment;

Oracle Invalid objects and invalid components;

What can I do?

As a first step, check for invalid objects and invalid components with the statements:

 SQL> select comp_name, version, status from dba_registry;
 SQL> select owner, object_name, object_id, object_type, created, last_ddl_time, timestamp, status from dba_objects where status != 'VALID' order by object_name;

Reset ORACLE_PATH (UNIX) or SQLPATH (WINDOWS) environment variable.

I hope this could help!

SQLPLUS - ORA-12547: TNS:lost contact

 Com usuário SIDADM em sistemas SAP, tentando acessar o banco com o usuário SYSDBA, se depara com a mensagem "ORA-12547: TNS:lost contact"

O que fazer?

Alguns passos úteis:

O problema pode estar relacionado compermissões, principamente em DBs executados com o usuário oracle. Neste caso vale ligar o suid bit para execução de binários do Oracle:

chmod 6751 $ORACLE_HOME/bin/*

Também é importante verificar o dono e grupo dono dos diretórios Oracle, no SAP, poderia ser como:

oracle:dba

É isto! Espero que ajude!

SAP SYBASE IQ:Deletando um DBFILE de uma DBSPACE

SAP SYBASE IQ:Deletando um DBFILE de uma DBSPACE




Suponha que seja necessário reduzir o tamanho total de uma DBSPACE no SAP IQ, por motivo de super dimencionamento .



O processo é relativamente simples, tomando alguns cuidados como um backup full da base de dados.





Suponha que exista a DBSPACE  IQ_1DBSPACE  com um tamanho total de 10GB com consumo de apenas 30%. É uma base que não crescerá muito é poderia ter o tamanho total de 5GB.



Pode-se checar o tamanho total da DBSPACE com a procedure:



sp_iqdbspace IQ_1DBSPACE;



Primeiro - verifique os DBFILES fazem parte da DBSPACE:



select convert(varchar(20), DBSpaceName), convert(varchar(20), DBFileName), convert(varchar(70), Path), DBFileSize, Usage, RWMode from sp_iqfile() where DBSpaceName = 'IQ_1DBSPACE';



DBSpaceName          DBFileName           Path                                                                   DBFileSize Usage
---------------------------------------------------------------------------------------------------------------------------------
IQ_1DBSPACE         IQ_1DBSPACE_001     /usr/sap/sybaseiq/sapdata/iq_1dbspace/dbs_iq_1dbspace_001             1G        30
IQ_1DBSPACE         IQ_1DBSPACE_002     /usr/sap/sybaseiq/sapdata/iq_1dbspace/dbs_iq_1dbspace_002             1G        30
IQ_1DBSPACE         IQ_1DBSPACE_003     /usr/sap/sybaseiq/sapdata/iq_1dbspace/dbs_iq_1dbspace_003             1G        30
IQ_1DBSPACE         IQ_1DBSPACE_004     /usr/sap/sybaseiq/sapdata/iq_1dbspace/dbs_iq_1dbspace_004             1G        30
IQ_1DBSPACE         IQ_1DBSPACE_005     /usr/sap/sybaseiq/sapdata/iq_1dbspace/dbs_iq_1dbspace_005             1G        30
IQ_1DBSPACE         IQ_1DBSPACE_006     /usr/sap/sybaseiq/sapdata/iq_1dbspace/dbs_iq_1dbspace_006             1G        30
IQ_1DBSPACE         IQ_1DBSPACE_007     /usr/sap/sybaseiq/sapdata/iq_1dbspace/dbs_iq_1dbspace_007             1G        30
IQ_1DBSPACE         IQ_1DBSPACE_008     /usr/sap/sybaseiq/sapdata/iq_1dbspace/dbs_iq_1dbspace_008             1G        30
IQ_1DBSPACE         IQ_1DBSPACE_009     /usr/sap/sybaseiq/sapdata/iq_1dbspace/dbs_iq_1dbspace_009             1G        30
IQ_1DBSPACE         IQ_1DBSPACE_010     /usr/sap/sybaseiq/sapdata/iq_1dbspace/dbs_iq_1dbspace_010             1G        30


Neste caso acima, poderiam ser deletados os DBFILES IQ_1DBSPACE_006, IQ_1DBSPACE_007, IQ_1DBSPACE_008, IQ_1DBSPACE_009 e IQ_1DBSPACE_010

Executar um backup full da base:

backup database FULL to '/usr/sap/backup/backup.dmp';

Após o backup full, colocar os DBFILES em modo Read Only:

alter dbspace IQ_1DBSPACE ALTER FILE IQ_1DBSPACE_006 readonly;
alter dbspace IQ_1DBSPACE ALTER FILE IQ_1DBSPACE_007 readonly;
alter dbspace IQ_1DBSPACE ALTER FILE IQ_1DBSPACE_008 readonly;
alter dbspace IQ_1DBSPACE ALTER FILE IQ_1DBSPACE_009 readonly;
alter dbspace IQ_1DBSPACE ALTER FILE IQ_1DBSPACE_010 readonly;

Pode-se verificar se os DBFILES estão em Read Only na coluna RWMode:

select convert(varchar(20), DBSpaceName), convert(varchar(20), DBFileName), convert(varchar(70), Path), DBFileSize, Usage, RWMode from sp_iqfile() where DBSpaceName = 'IQ_1DBSPACE';

Se estiver Okay, iniciar a migração dos dados para os DBFILES de 001 à 005:

sp_iqemptyfile 'IQ_1DBSPACE_006';
sp_iqemptyfile 'IQ_1DBSPACE_007';
sp_iqemptyfile 'IQ_1DBSPACE_008';
sp_iqemptyfile 'IQ_1DBSPACE_009';
sp_iqemptyfile 'IQ_1DBSPACE_010';

Após esvaziar os DBFILES, conferir o status:


select convert(varchar(20), DBSpaceName), convert(varchar(20), DBFileName), convert(varchar(70), Path), DBFileSize, Usage, RWMode from sp_iqfile() where DBSpaceName = 'IQ_1DBSPACE';



DBSpaceName          DBFileName           Path                                                                   DBFileSize Usage
---------------------------------------------------------------------------------------------------------------------------------
IQ_1DBSPACE         IQ_1DBSPACE_001     /usr/sap/sybaseiq/sapdata/iq_1dbspace/dbs_iq_1dbspace_001             1G        60
IQ_1DBSPACE         IQ_1DBSPACE_002     /usr/sap/sybaseiq/sapdata/iq_1dbspace/dbs_iq_1dbspace_002             1G        60
IQ_1DBSPACE         IQ_1DBSPACE_003     /usr/sap/sybaseiq/sapdata/iq_1dbspace/dbs_iq_1dbspace_003             1G        60
IQ_1DBSPACE         IQ_1DBSPACE_004     /usr/sap/sybaseiq/sapdata/iq_1dbspace/dbs_iq_1dbspace_004             1G        60
IQ_1DBSPACE         IQ_1DBSPACE_005     /usr/sap/sybaseiq/sapdata/iq_1dbspace/dbs_iq_1dbspace_005             1G        60
IQ_1DBSPACE         IQ_1DBSPACE_006     /usr/sap/sybaseiq/sapdata/iq_1dbspace/dbs_iq_1dbspace_006             1G        1
IQ_1DBSPACE         IQ_1DBSPACE_007     /usr/sap/sybaseiq/sapdata/iq_1dbspace/dbs_iq_1dbspace_007             1G        1
IQ_1DBSPACE         IQ_1DBSPACE_008     /usr/sap/sybaseiq/sapdata/iq_1dbspace/dbs_iq_1dbspace_008             1G        1
IQ_1DBSPACE         IQ_1DBSPACE_009     /usr/sap/sybaseiq/sapdata/iq_1dbspace/dbs_iq_1dbspace_009             1G        1
IQ_1DBSPACE         IQ_1DBSPACE_010     /usr/sap/sybaseiq/sapdata/iq_1dbspace/dbs_iq_1dbspace_010             1G        1


Verificar se os DBFILES estão prontos para remoção na coluna OkToDrop:

select convert(varchar(20), DBSpaceName), convert(varchar(20), DBFileName), DBFileSize, Usage, RWMode, OkToDrop  from sp_iqfile() where DBSpaceName = 'IQ_1DBSPACE';


DBSpaceName          DBFileName           DBFileSize Usage RWMode OkToDrop
--------------------------------------------------------------------------
IQ_1DBSPACE         IQ_1DBSPACE_001     1G        60    RW     N
IQ_1DBSPACE         IQ_1DBSPACE_002     1G        60    RW     N
IQ_1DBSPACE         IQ_1DBSPACE_003     1G        60    RW     N
IQ_1DBSPACE         IQ_1DBSPACE_004     1G        60    RW     N
IQ_1DBSPACE         IQ_1DBSPACE_001     1G        60    RW     N
IQ_1DBSPACE         IQ_1DBSPACE_006     1G        1     RO     Y
IQ_1DBSPACE         IQ_1DBSPACE_007     1G        1     RO     Y
IQ_1DBSPACE         IQ_1DBSPACE_008     1G        1     RO     Y
IQ_1DBSPACE         IQ_1DBSPACE_009     1G        1     RO     Y
IQ_1DBSPACE         IQ_1DBSPACE_010     1G        1     RO     Y


Apagar os DBFILES da DBSPACE:

ALTER DBSPACE IQ_1DBSPACE DROP FILE IQ_1DBSPACE_006;
ALTER DBSPACE IQ_1DBSPACE DROP FILE IQ_1DBSPACE_007;
ALTER DBSPACE IQ_1DBSPACE DROP FILE IQ_1DBSPACE_008;
ALTER DBSPACE IQ_1DBSPACE DROP FILE IQ_1DBSPACE_009;
ALTER DBSPACE IQ_1DBSPACE DROP FILE IQ_1DBSPACE_010;

Verificar a DBSPACE:

select convert(varchar(20), DBSpaceName), convert(varchar(20), DBFileName), DBFileSize, Usage, RWMode, OkToDrop  from sp_iqfile() where DBSpaceName = 'IQ_1DBSPACE';


DBSpaceName          DBFileName           DBFileSize Usage RWMode OkToDrop
--------------------------------------------------------------------------
IQ_1DBSPACE         IQ_1DBSPACE_001     1G        60    RW     N
IQ_1DBSPACE         IQ_1DBSPACE_002     1G        60    RW     N
IQ_1DBSPACE         IQ_1DBSPACE_003     1G        60    RW     N
IQ_1DBSPACE         IQ_1DBSPACE_004     1G        60    RW     N
IQ_1DBSPACE         IQ_1DBSPACE_001     1G        60    RW     N


Pode-se ainda executar um check na base de dados após a manobra:

sp_iqcheckdb 'check database';

Analise High load SAP HANA

Notas:

1804811 - SAP HANA Database: Kernel Profiler Trace

Solution 

Connect to your HANA database server as user sidadm (for example via putty) and start hdbcons by typing command "hdbcons".
To do a Kernel Profiler Trace of your query, please follow these steps:

1. "profiler clear" - Resets all information to a clear state

2. "profiler start" - Starts collecting information.

3. Execute the affected query.

4. "profiler stop" - Stops collecting information.

5. "profiler print -o /path/on/disk/cpu.dot;/path/on/disk/wait.dot" - writes the collected information into two dot files which can be sent to SAP.

Attention: Specifying both a database user and an application user with SAP HANA SPS <= 10 can result in a crash. This problem is fixed as of SAP HANA SPS 11.

1732157 - Collecting diagnosis information for SAP HANA [VIDEO]

1813020 - How to generate a runtime dump on SAP HANA 

1) From the OS Level

1) Log into the linux HANA host presenting the issue as sidadm user;

2) Run command 'hdbcons';

3) On the hdbcons console run command below:

 > runtimedump dump

This will create a runtimedump for the host you logged in. The generated file will be under traces directory with naming like 'indexserver....rtedump.trc'.

4) Attach generated trace file to the OSS Message

Na prática

1. generate a kernel profiler trace. Please refer to SAP note 1804811

• 1. "profiler clear" - Resets all information to a clear state
• 2. "profiler start" - Starts collecting information.
• 3. Execute the affected query. - in the case of our problem, it is not necessary
• 4. "profiler stop" - Stops collecting information.
• 5. "profiler print -o /hana/shared/SID/HDB00/serverXX/trace//wait.dot" - writes the collected information into two dot files which can be sent to SAP.

2 . generate 3 runtime dumps with 2 minutes interval between each. These must be generated DURING the system hang. Please refer to 1813020.

• cd /hana/shared/SID/HDB00/serverX/trace/      
• exec /hana/shared/rtedump_script.sh

3. generate a full system dump as per note 1732157 during the time frame of the high cpu.

cd /usr/sap/SID/HDB00/exe/python_support/

python fullSystemInfoDump.py

cd /usr/sap/SID/SYS/global/sapcontrol/snapshots/

ls –larth

Copy the newer files on diretory

https://mdocs.sap.com/mcm/public/v1/open?shr=4gWUBQ4vmFEZgvk8Ycyq_yS42_iwt0-hDFrQPOu6MVE

PARA executar tudo em um comando (copiar e colar na linha de comando e lembrar de alterar serverX pelo nome correto do servidor):

hdbcons "runtimedump dump" ; hdbcons  "profiler clear" ; hdbcons   "profiler start" ; hdbcons  "profiler stop" ; hdbcons   "profiler print -o /hana/shared/SID/HDB00/serverX/trace/wait.dot" ; cd /hana/shared/SID/HDB00/serverX/trace/  ; /hana/shared/rtedump_script.sh ; cd /usr/sap/SID/HDB00/exe/python_support/ ; python fullSystemInfoDump.py

Depois da execução, proceder com a coleta, compressão e envio do arquivo para a SAP.

Executar $hdbcons "runtimedump dump"

hdbcons  "profiler clear"

hdbcons   "profiler start" hdbcons  "profiler stop" hdbcons   "profiler print -o /hana/shared/SID/HDB00/backup/wait.dot"

verificar qual thread consome mais recursos:

top -H -u sidadm

Guardar este número para procurar nos dumps

listar threads:

ps -eLf

Executar $hdbcons "runtimedump dump"

hdbcons  "profiler clear"

hdbcons   "profiler start" hdbcons  "profiler stop" hdbcons   "profiler print -o /hana/shared/SID/HDB00/backup/wait.dot"

Dicas LVM / TIPS and Tricks LVM

Resize com LVM

- Adicionar o novo disco e criar a partição:

  # fdisk /dev/sdb (id 8e)

- visualiza todos os lvm

  # lvdisplay

- ver LVM com:

  # vgs

  # lvs

  # pvs

- Criar PV

  # pvcreate /dev/sdb1

- Criar VG

  # vgcreate vg1 /dev/sdc1

- Criar LV

  # lvcreate -L "tamanho" -n "device" vg0

- Extendendo PV

# pvresize --setphysicalvolumesize 40G /dev/sda1 

  

- Extendendo VG

  # vgextend vg0 /dev/sdb1

- extendendo LVM

  # lvextend -L 5G /dev/vg0/opt (tamanho da partição será 5gb)

  # resize2fs -p /dev/vg0/opt

- reduzindo LVM

  # e2fsck -f /dev/vg0/opt (sempre rodar FSCK antes de realizar resize)       

  # resize2fs /dev/vg0/opt 10G (margem de 10% de segurança)

  # lvreduce -L 10G /dev/vg0/opt (tamanho da partição será 10gb)

- removendo disco do VG

  # vgreduce vg0 /dev/sdb1

- extendendo PV

  # pvresize /dev/sdb

- crescer LVM em SWAP

# swapoff -a

# lvextend -L 5G /dev/vg0/swap (tamanho da partição será 5gb)

# mkswap /dev/vg0/swap

# swapon -a

SQL Oracle 1 e SAP - Dicas

--Long RAW TABLES--------------------------------------------------------------------

select
   owner c1,
   table_name c2,
   pct_free c3,
   pct_used c4,
   avg_row_len c5,
   num_rows c6,
   chain_cnt c7,
   chain_cnt/num_rows c8,
   tablespace_name c0
from dba_tables
where
owner not in ('SYS','SYSTEM')
and
table_name in
 (select table_name from dba_tab_columns
where
 data_type in ('RAW','LONG RAW','CLOB','BLOB','NCLOB')
 )
and
chain_cnt > 0
order by chain_cnt desc
;

--LONG RAW TABLES--------------------------------------------

select table_name,data_type from dba_tab_columns
where
 data_type in ('RAW','LONG RAW','CLOB','BLOB','NCLOB');



 --LONG Raw tables and tablespaces status--------------------------------------

 select table_name, tablespace_name, num_rows, cluster_owner, PCT_USED, LAST_ANALYZED, DEPENDENCIES, (BLOCKS * 8192)     from dba_tables where tablespace_name = 'TABLESPACE' order by num_rows desc;




--ORACLE JOBS PROGRESS----------------------------------------------------------

SELECT sid, to_char(start_time,'hh24:mi:ss') stime,
message,( sofar/totalwork)* 100 percent
FROM v$session_longops
WHERE sofar/totalwork < 1;

--ORACLE LONGOPS----------------------------------------------------------------

select * from v$session_longops

--Searching for a SID session---------------------------------------------------

select
*
from
   v$session
where
   sid = SID;

--Searching for a background job exhibiting some details------------------------ 

   SELECT s.inst_id,
       s.sid,
       s.serial#,
       p.spid,
       s.username,
       s.program
FROM   gv$session s
       JOIN gv$process p ON p.addr = s.paddr AND p.inst_id = s.inst_id
WHERE  s.type != 'BACKGROUND'
ORDER BY SID;

--Killing a session-------------------------------------------------------------

alter system kill session 'SID,SERIAL';



--DATAPUMP JOBS-----------------------------------------------------------------

select * from dba_datapump_jobs;

--Showing tables from a tablespace----------------------------------------------

select * from dba_tables where TABLESPACE_NAME ;

desc sys.dba_free_space

--Free space of a tablespace----------------------------------------------------

SELECT TABLESPACE_NAME,SUM(FREEMB),SUM(CONTIGUOMB)
FROM
(select tablespace_name,FILE_ID
                      , round(sum(bytes)/1024/1024,2) FreeMb
                      , round(max(bytes)/1024/1024,2) ContiguoMb
from sys.dba_free_space where tablespace_name='TABLESPACE'
group by tablespace_name,FILE_ID
having round(max(bytes)/1024/1024,2) > 70)
GROUP BY tablespace_name
ORDER BY tablespace_name;


--Free space of a tablespace----------------------------------------------------

select
   a.tablespace_name,
   a.bytes_alloc/(1024*1024) "TOTAL ALLOC (MB)",
   a.physical_bytes/(1024*1024) "TOTAL PHYS ALLOC (MB)",
   nvl(b.tot_used,0)/(1024*1024) "USED (MB)",
   (nvl(b.tot_used,0)/a.bytes_alloc)*100 "% USED"
from
   (select
      tablespace_name,
      sum(bytes) physical_bytes,
      sum(decode(autoextensible,'NO',bytes,'YES',maxbytes)) bytes_alloc
    from
      dba_data_files
    group by
      tablespace_name ) a,
   (select
      tablespace_name,
      sum(bytes) tot_used
    from
      dba_segments
    group by
      tablespace_name ) b
where
   a.tablespace_name = b.tablespace_name (+)
and
   a.tablespace_name not in
   (select distinct
       tablespace_name
    from
       dba_temp_files)
and
   a.tablespace_name not like 'UNDO%'
   AND a.tablespace_name like '%TABLESPACE%'
order by 1;

--Space of a table--------------------------------------------------------------

select segment_name,segment_type,bytes/1024/1024 MB from dba_segments where segment_type='TABLE' and segment_name='USER'.'TABLE';

--Size of a table---------------------------------------------------------------

SELECT DS.TABLESPACE_NAME, SEGMENT_NAME, ROUND(SUM(DS.BYTES) / (1024 * 1024)) AS MB
  FROM DBA_SEGMENTS DS
  WHERE SEGMENT_NAME IN (SELECT TABLE_NAME FROM DBA_TABLES) and SEGMENT_NAME like 'TABLE'
 GROUP BY DS.TABLESPACE_NAME,
       SEGMENT_NAME;
     
--Abort a Redef table job-------------------------------------------------------   

BEGIN
DBMS_REDEFINITION.ABORT_REDEF_TABLE(
   uname       => 'USER',
   orig_table  => 'Table Origem',
   int_table   => 'Tabela destino#$');
END;


--Verifica paralelismo de um indice

select degree from dba_indexes where index_name LIKE 'indice';

Links úteis SAP IQ

Links úteis SAP IQ

https://launchpad.support.sap.com/#/incident/pointer/002075129400003642812017

https://launchpad.support.sap.com/#/notes/1910965

https://help.sap.com/viewer/a893f37e84f210158511c41edb6a6367/16.0.11/en-US/a87fbd6184f2101599e284403f769f66.html

https://blogs.sap.com/2014/04/30/sap-sybase-iq-how-to-restore-your-backups-to-another-system/

http://www.rocket99.com/techref/8746.html

https://help.sap.com/saphelp_iq1608_iqbackup/helpdata/en/a6/236d0484f2101591fabb9064294f1d/frameset.htm

Troubleshooting SAP IQ e BACKUP/RESTORE

Troubleshooting IQ

Verificar situação dos discos / RAW Devices

Verificar catalogo de arquivos no IQ:  SELECT * FROM SYS.SYSDBFILE;

Verificar Header dos arquivos: iqheader


Comandos úteis:

Conectar no banco
dbisql -c "uid=dba;pwd=senha" -host localhost -port 2741 -nogui

Verificar header do backup:

db_backupheader

Procedures e SQL:

Espaço:
sp_iqdbspace

sp_iqfile

Alterar ou deletar dbfiles:

alter dbspace DBSPACE drop file "nome_arquivo"'

select Value from sp_iqstatus() where name like '%Main IQ Blocks Used%';

Backup:

backup database full to @BackupFileName

Verificar status do banco com filtro:

select Value from sp_iqstatus() where name like '%Main IQ Blocks Used%';
go



Restore do sistema:

Pré requisitos: os dbfiles do sistema devem ter o mesmo tamanho do banco original na mesma quantidade. O sistema destino deve ter a mesma versão da origem ou versão superior.

Iniciar em modo utility_db: start_iq -n utility_db -iqmc 40000 -iqtc 60000

Executar Restore:

dbisql -nogui -c "uid=DBA;pwd=senha;eng=utility_db;dbn=utility_db"

RESTORE database 'caminho_do_backup/DATABASE.db'
FROM 'arquivos_de_backup.dmp sem stripe';

Upload de nova versão de EPM no download center do BPC

Para upload de nova versão de EPM no download center do BPC:

Link: https://help.sap.com/doc/4c5f3dca0ead4cfb9105d18a1efeef24/10.0.28/en-US/EPMofc_10_install_en.pdf

Procedure
1. Do one of the following:
? If your version of SAP NetWeaver BW is prior to the SAP_BW Release 730 SP3, you must implement the
following SAP Notes: 1558149, 1553052, 1578760 and 1547050.
? If your version of SAP NetWeaver BW is 740, 750, 800, 801 or 810, you must implement the following SAP
Note: 2369339.
? If you need to install EPM add-in Support Package 27 or upper versions for the x64 edition, from the
Planning and Consolidation web client, please upgrade Planning and Consolidation accordingly. See SAP
note 2403723.
2. Log on to SAP NetWeaver and execute the RSBPCLD transaction.
3. In the Program field, enter UJ0_FILE_UPLOAD and click Execute (F8).
The Upload window opens.
4. In the Option and version section, select the type of update you want to perform depending on whether or not
the support package is mandatory.
EPM Add-in for Microsoft Office Installation Guide
Installing the EPM Add-in for Microsoft Office C U S T O M E R 19
Option Description
Force update
When updates are defined as "force update", a message pops up on your local machine, prompting you to
install the update. If you do not install the update, you will not be able to use the EPM add-in.
The version XXX of the EPM Add-in is now available. It must be installed before you can use the EPM Add-in
Auto update
When updates are defined as "auto update", a message pops up every time an update is available, prompting
you whether you want to install it now or later.
"Version xxx of the EPM Add-in is now available. Do you want to install it?
User update
When updates are defined as "user update", if you choose the Notify me when updates are
available option, a message pops up every time an update is available, prompting you whether you want
to install it now or later.
"Version xxx of the EPM Add-in is now available. Do you want to install it?
You can choose to select the Do not show this message again option.
5. In the File version field, enter the EPM Add-in version number (for example: 10.0.0.5054).
6. Select the Full Installer type.
7. In the Upload section, click Browse to select the EPM Add-in.exe file and then click Upload.
The Enter Transport Request dialog box opens.
8. Click the New icon.
The Select Request Type dialog box opens.
9. Select Customizing Request and validate.
The Create Request dialog box opens.
20 C U S T O M E R
EPM Add-in for Microsoft Office Installation Guide
Installing the EPM Add-in for Microsoft Office
10. Enter a short description text and click the Save icon.
11. In the Enter Transport Request dialog box, click the Validate icon.
12. Once the transport has been created, open the Transport Management System.
13. In the Import Queue of your system, select the transport you created and click Import.
Next Steps
To perform an upgrade of the EPM add-in on the server, follow the same procedure


Para verificar versões disponíveis :

SE16 -> RSBPC0_AUTO_UPDT ou UJ0_AUTO_UPDATE


Ver link: https://wiki.scn.sap.com/wiki/display/CPM/Understanding+the+UJ0_FILE_UPLOAD+Options+for+EPM+Add-in+Client+For+BPC+10+NW

Carga entre SAP BW e SAP ERP com IDOCS parados na SM58

A carga entre SAP BW e SAP ERP com IDOCS parados na SM58

Sintomas :

IDOCs ficam parados na SM58 e não chegam no BW.

O QOUT fica em status Waiting.

Execução LUW faz IDOC chegar no BW.

Solução:

Procurar por processos bloqueando a execução tRFC e qRFC, normalmente processos com longo tempo de duração na sm66/sm50

Material para consulta:

https://wiki.scn.sap.com/wiki/display/ABAPConn/Outbound+Scheduler+%28SMQS%29+remains+in+status+WAITING

.

Alterar número de processos na SUM após inicio do Update/Upgrade

Como alterar número de processos na SUM após inicio do Update/Upgrade:

Acessar a url  http://servidor_sap:1128/lmsl/sumabap/PHM/set/procpar  e alterar o número de processos.

DICA - ERROR: Tipo de IDOC XXXXXXX do BW diferente do tipo de IDOC do sistema fonte.

Source system no BW, ao checar aparece o erro:

BW desconhecido sistema fonte

ou

tipo de IDOC XXXXXXX do BW diferente do tipo de IDOC do sistema fonte.


Soluções possíveis:

verificar RFCs, usuários e permissões;

Verificar se entradas das tabelas EDIPORT e EDIPOA estão iguais - nota SAP 110849

Verificar intervalo de numeração de portas disponiveis na transação snum - nota 110849
--------------------------------------------------------------------------------------------------------------------------

Nota 110849:

Symptom
"Error during insert in port table" during creation of source system.

Other Terms
SourceSystem, porttable

Reason and Prerequisites
You get the error message "Error during insert in port table (E0 552)" during creation of a source system. "Please enter a valid receiver port" E0420

Solution
Take a look at table EDIPORT of your BW system and note the next free number for the field "Port". This is the adjacent number of the highest entry like 'A0000000123' for example. In this case e.g. take '124'.
Choose transaction "snum" and object "ediport".
Select "number ranges" from the menu "Goto" and here the button "status".
Change the CURRENT NUMBER of the ranges to the next free number you noted from table EDIPORT.

If the number range of your BW system is correct please check the same in your OLTP system.

Check inconsistency (port) between tables EDIPOA and EDIPORT.
If affected port is only exists in EDIPOA table, delete the entry from EDIPOA.

Also reset the buffering for all servers on system via transaction /$tab

Transactions for SAP ERP administration

Programming and Debugging

Transaction	Description
SE80	Abap Development WorkBench
*SE38	Abap Editor. Shows source code, attributes, documentation, variants and text elements.
*SE37	Manage Function modules. It can create, display or edit them.
*SE24	Manage Classes. It can create, display or edit them.
*SE11	ABAP Dictionary.
ST22	Abap Runtime Error. You can filter by a lot of parameters.
ST11	Developer traces. Shows error log files, contain error files from each Dialog.
SU53	Permissions Issue Solver
ST01	System Trace (authorization checks). Used by programmers to find errors in authorizations.
SM30	Show Tables
SE16	Maintain Tables
SE16N	Maintain Tables (stronger).
SE18	BADI Builder
SICF	WebDynpro Access. Shows the graphical screens.
SE51	Screen Painter (Creates WebDynpro screens)

System Maintenance

Transaction	Description
SM50	Shows process overview of the SAP system, including Dialogs, Spoolers, background jobs and update jobs.
SM66	Global Work Process Overview
SM51	Show all SAP Servers in the Landscape.
SLG1	Analyzes logs from the System. It has filters like: user, transaction and program that triggered the log.
RZ20	System Monitoring. You can monitore a lot of events on the system. This transaction can run for others systems.
RZ70	System Landscape Directory: Administration
--	--
SP02	Show global spool request list.
SM37	View System_Wide Jobs
AL08	List of users logged in on the server. It shows users logged on into each client.
SM04	List logged in users. Better view.
SU01	User Maintenance.
SU3	Maintain User Profile (normally you don't have authorization with SU01).
SU01D	Display User (normally you don't have authorization with SU01).
PFCG	Role Maintenance.
SM13	Shows Update Requests. Also, show who and when it was requested.
SM59	Config RFC connections
SM12	Lock Tables
SM21	System Log
AL11	SAP Explorer. Show directory structures from the SAP system and permits you to display files.
SE95	Modification Browser: Shows which notes were applied, BADis activated and objects modified. Very good T-code.
--	--
SNOTE	Note Assistant. Transaction that shows implemented notes, notes to be implemented and other details regarding SAP notes.
SMSY	SAP Solution Manager (doesn't contain per default).
SPAM	Support Package Manager (upgrades)
SAINT	Add-on Installation Tool
SBWP	Business Workplace
--	--
SE09	Transport Organizer
SE10	Transport Organizer
SE01	Transport Organizer (Extended View)
STMS	Transport Management System
SWDD	Workflow builder. Let's you check and customize the workflows visually.

User Specific

Transaction	Description
SUIM	User Information System. Shows details about the user and its roles.
SM36	Define Background Job
SMX	View own jobs
/O	Show Opened Sessions
/N	Goto Sap Easy Access

Background Processing

Transaction	Description
RZ01	Job Scheduling Monitor
RZ04	CCMS: Maintain Operation Modes/Instance
SM36	Define Background Job
SM37	Simple Job Selection
SM37C	Extended Job Selection
SM49	External Operating System Commands
SM61	Bacground Controller List
SM62	Event History
SM64	Background Events
SM65	Analysis Tool - Background Processing
SM69	External Operating System Commands
SMX	Job Overview

Documentation

Transaction	Description
SE81	Application Hierarchy. Shows all the abbreviations for all of the components. On double-click, opens the package on the SE80.
ABAPDOCU	Abap Documentation and Examples. The examples are very intuitive.
SEARCH_SAP_MENU	Search by text for items in the SAP Menu.
SEARCH_USER_MENU	Search by text for items in the User Menu.

Error Current imported l_th_trkorr_import_all has 2 (lines) in TP command Fatal error: Import all mismatch

Transport 

Post-import methods for change/transport request: xxxxxxxxxxxxx

Post-import method RS_AFTER_IMPORT started for TRFN L, date and time: xxxxxxxxxxx
Invalid objects: 'After Import' terminated (see long text)

Error Current imported l_th_trkorr_import_all has 2 (lines) in TP command Fatal error: Import all mismatch

Error xxxxxxxxxxxxxxxx (0008) in TP command Returncode of trkorr trkorr_no_1
Errors occurred during post-handling RS_AFTER_IMPORT for TRFN L
The errors affect the following components:
   BW-WHM-MTD (Metadata (Repository))
Post-import methods of change/transport request xxxxxxxxx completed

Error Current imported l_th_trkorr_import_all has 2 (lines) in TP command Fatal error: Import all mismatch

.

.

.

ended with return code:  ===> 12 <===

Solution:

In program

SAP_RSADMIN_MAINTAIN

Include:

OBJECT = RSVERS_BI_IMPORT_ALL
VALUE  = <SPACE>

Notes:

1385869 - Parallel execution of BI after-import methods 

1626202 - Control of after import processing in the case of errors   

1793833 - Import All: Incorrect request marked for RC = 12 

1556801 - Restrictions for IMPORT ALL in relation to BW objects 

1115759 - Error during import of BI objects with "Import all"