Criando Oracle DBLINK

Arquivo tnsnames.ora
- Na máquina onde o dblink será criado, configure o arquivo $ORACLE_HOME/network/admin/tnsnames.ora.
- Adicione uma entrada como o exemplo abaixo.

> Modelo
<SID>.WORLD =
  (DESCRIPTION =
   (SDU = 32768)
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = IP)(PORT = 1521))
    )
     (CONNECT_DATA =
      (SID = <sid>)
      (GLOBAL_NAME = <SID>.WORLD)
     )
  )

onde, 

SID = É o nome do seu banco de dados remoto.

> Exemplo

TST.WORLD =
  (DESCRIPTION =
   (SDU = 32768)
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = 10.0.0.3)(PORT = 1521))
    )
     (CONNECT_DATA =
      (SID = tst)
      (GLOBAL_NAME = TST.WORLD)
     )
  )

Criando DBLINK
- Na instancia onde se deseja criar o dblink.

> Modelo

CREATE PUBLIC  DATABASE LINK  Name

   CONNECT TO Name IDENTIFIED BY User

   USING 'SID'; 

onde,

Name = Nome do seu link

User = Usuário do banco de dados remoto que será utilizado para se identificar

SID = O nome da instancia remota (o mesmo utilizado dentro do arquivo tnsnames.ora)

> Exemplo

CREATE PUBLIC  DATABASE LINK  LTST

   CONNECT TO LTST IDENTIFIED BY ltst

   USING 'TST'; 

Abraços

Mais informações

Start Stop SAP via Script

Start SAP
#/usr/bin/su - <SID>adm -c startsap

Stop SAP
#/usr/bin/su - <SID>adm -c stopsap

Mais informações

SAP Basis, Administração, Implementação, Monitoramento | DTecno Consultoria

DTecno Consultoria 

A DTecno Consultoria é especializada em administração do módulo SAP Basis em todas as camadas, aplicação, banco de dados, hardware e backup.

Site:
http://www.dtecno.com.br

Keywords:
DTecno, DTecno Consultoria,DTecno Minas Gerais, OutSourcing SAP, DTecno OutSourcing, Consultoria SAP, Consultoria Oracle SAP, Consultoria SAP Sul de Minas, Consultoria SAP Minas Gerais, DTecno SAP,Consultoria IBM Sul de Minas, DTecno Aix, DTecno Oracle, Oracle, IBM, Aix, IBM

Mais informações

SUM - The file /usr/sap//SUM/sdt/.lock could not be locked. Check the write permissions and whether the controller is already started.

Problema

maq1:maqadm 23> STARTUP

*** Checking if C++ runtime is installed ...

*** Starting from /usr/sap/<SID>/SUM/sdt...

** Checking username "maqadm" for compliance...

Mar 17, 2014 1:42:04 PM [Error]: The file /usr/sap/<SID>/SUM/sdt/.lock could not be locked. Check the write permissions and whether the controller is already started.

Mar 17, 2014 1:42:04 PM [Fatal]: Error during controller startup.

Mar 17, 2014 1:42:04 PM [Fatal]: SL Controller exiting.

Solução

- Exclua os arquivos:

 -> /usr/sap/<SID>/SUM/sdt/data/.sdt_keystore

 ->/usr/sap/<SID>/SUM/sdt/data/.sdt_storage

- Inicie o SUM normalmente.

Mais informações

Notas SDCC RFC e OSS

763561 - Service Data Control Center (SDCCN) - FAQ
216952 - Service Data Control Center (SDCC) - FAQ

Mais informações

Transport control program tp ended with error code 0016

Problema

ERROR: stopping on error 16 during DD IMPORT

Transport control program tp ended with error code 0016

Solução

- Verifique se os arquivos data e cofile da request em questão foram enviados no formato binário.

- Verifique as permissões dos arquivos da request em questão nos diretórios data e cofile.

Abraços

Mais informações

Drive xxxx firmware level is unsupported

Problema

==============================================================================================================|

|    4301 |    9 |    20140305155337 |      1 |     Warning |     5005076b074ebaff |         0 |      Unmasked |

|--------------------------------------------------------------------------------------------------------------|

| Msg: Drive 01:05 firmware level is unsupported.                                                              |

Solução

- Para verificar a versão do firmware utilizado, siga os passos:

<CLI> detail drive -slot 1:4

Current Machine Local Time: 03/05/2014  02:31:16 PM

 __________________________________________________________________________________________________________

| Drive#|  E:T  | SerialNo  |  Cap  |    Pool     | Usage | State | Mount State |Ctl0|Ctl1|  RPM  |FW level|

|_______|_______|___________|_______|_____________|_______|_______|_____________|____|____|_______|________|

|      3|  1:4  |   3SK012N2|  419GB|       Array2|    GRP|     OK|       Online|   1|   1|  15000|    BA5A|

|_______|_______|___________|_______|_____________|_______|_______|_____________|____|____|_______|________|

Drive SAS Address                 : 5000c5000079cb63

Vendor / Manufacturer ID          : IBM-ESXS

IBM Option Number                 : 44W2239

IBM FRU Number                    : 42D0573

IBM Part Number                   : 44W2243

Interface Type                    : SAS

Disk Speed                        : 15000

Serial Number                     : 3SK012N2

Code Level                        : BA5A

Product Master ID                 : 41Y8485

Product Family ID                 : ST3450857SS

 ________________________________________

|      Volume     |  RaidType  |   Size  |

|_________________|____________|_________|

|Array2:LPCPR_v1|           5|     50GB|

|   Array2:LP1_v2|           5|     40GB|

|Array2:LPCPR_v2|           5|    100GB|

|Array2:LPCPR_v3|           5|    100GB|

|_________________|____________|_________|

<CLI> detail drive -slot 1:5

Current Machine Local Time: 03/05/2014  02:31:36 PM

 __________________________________________________________________________________________________________

| Drive#|  E:T  | SerialNo  |  Cap  |    Pool     | Usage | State | Mount State |Ctl0|Ctl1|  RPM  |FW level|

|_______|_______|___________|_______|_____________|_______|_______|_____________|____|____|_______|________|

|      4|  1:5  |   LWY7R07S|  419GB|          -- |    GLS|     OK|       Online|   1|   1|  15000|    A3C2|

|_______|_______|___________|_______|_____________|_______|_______|_____________|____|____|_______|________|

Drive SAS Address                 : 5000cca02ab71ee4

Vendor / Manufacturer ID          : IBM-ESXS

IBM Option Number                 : 44W2239

IBM FRU Number                    : 42D0573

IBM Part Number                   : 44W2243

Interface Type                    : SAS

Disk Speed                        : 15000

Serial Number                     : LWY7R07S

Code Level                        : A3C2

Product Master ID                 : 41Y8495

Product Family ID                 : VPCA450900EST1

 ________________________________________

|      Volume     |  RaidType  |   Size  |

|_________________|____________|_________|

|_________________|____________|_________|

<CLI>

- Segue tabela de tipos de usos dos discos.

The usage definitions are:

·         UNA - UnAssigned

·         GRP/SGR - Current/Stale Group Member

·         FOR - Foreign

·         GLS/SGS - Current/Stale Global Spare

- Verifique se o disco em questão é o stale global spare, se for, basta apenas mascarar o warning.

Abraços

Mais informações

SAP Data Archiving - References

http://help.sap.com/saphelp_srm30/helpdata/en/15/c9df3b6ac34b44e10000000a114084/content.htm
http://help.sap.com/SAPHELP_NW04S/helpdata/EN/43/f0ed9f81917063e10000000a1553f6/content.htm

Mais informações

Aplicação de Technical Level

Before you begin the installation of this package, please note the following: 1.    You must be logged in as the root user to install this package. 2.    IBM recommends creating a system backup before starting the installation procedure. 3.    The latest AIX installation hints and tips for your version of AIX are available from the IBM Subscription service for Unix and Linux web site: http://www14.software.ibm.com/webapp/set2/subscriptions/pqvcmjd These tips contain important information that should be reviewed before installing this update. 4.    IBM recommends creating a separate file system for/usr/sys/inst.images for the following reasons: o    Downloaded fix packages require a significant amount of disk space. o    By creating a separate file system, you prevent the expansion of the/usr file system.

Follow these steps to install the update package: 1.    Always run the inutoc command to ensure the installation subsystem will recognize the new fix packages you download. This command creates a new .toc file for the fix package. Run the inutoc command in the same directory where you downloaded the package filesets. For example, if you downloaded the filesets to /usr/sys/inst.images, run the following command: inutoc /usr/sys/inst.images (Optional): Renaming the *.bff files is not necessary, but does help you see which filesets are affected by the downloaded files. To rename the downloaded files to their fileset name, run the bffcreate command. After renaming the files, run the inutoc command again. For example, if you downloaded the filesets to /usr/sys/inst.images, run the following command to rename them: bffcreate -c -d /usr/sys/inst.images  2.    For all updates To install all updates from this package that apply to the installed filesets on your system, use the following command: smit update_all It is highly recommended that you apply all updates from this package.  3.    Reboot the system. A reboot is required for this update to take effect.

You may wish to retain this package for future use. When you install additional operating system software you will want to use this package to bring the additional software up to this level. You can create a list of the APARs closed in this package, which you can then view (and search) in an ASCII editor, such as vi or emacs. First, create the .toc file for the package by using the inutoc command described above. Then, run the following command to extract the APAR listings from the .tocfile: grep ^I .toc > apar.list Run the following command to eliminate duplicate entries from the apar.listfile: sort -u apar.list -o sorted.apars

Font: IBM

Mais informações

Aix Technical Level e Service Pack - 02/2014

Mais informações