Configurar saprouter para aceitar conexoes de fora
Olha sei que este topico ja foi aberto mas volto a pedir um suporte. Preciso me conectar ao meu SAP de casa, tenho no meu saprouttab o seguinte:
# SNC connection to and from SAP
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 194.39.131.34 *
# SNC connection to local system for R/3-Support
# R/3 Server: 192.168.1.1
# R/3 Instance: 00
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 10.1.1.15 3200
# SNC connection to local WINDOWS system for WTS, if applicable
# Windows server: 192.168.1.2
# Default WTS port: 3389
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 10.1.1.15 3389
# SNC connection to local UNIX system for SAPtelnet, if applicable
# UNIX server: 192.168.1.3
# Default Telnet port: 23
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 10.1.1.15 23
# SNC connection to local Portal system for URL access, if applicable
# Portal server: 192.168.1.4
# Port number: 50003
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 10.1.1.15 50003
# Access from the local Network to SAP
P 10.1.1.15 194.39.131.34 3299
# Permitir todas as redes temporariamente
P * * *
# deny all other connections
D * * *
Ja coloquei no meu SAPGui a seguinte string:
/H/<IP PUBLICO DA FIREWALL>/S/3299/H/
IP - 10.1.1.15 = IP Do servidor de SAPRouter que é o mesmo Servidor que correr o SAP ECC 6.
So que mesmo assim nao consigo conectar-me, o que estará errado aqui.
cumprimentos.
Bom dia!
Estou tentando configurar o SAP ROUTER para possbilitar conexões a partir de uma rede externa. Entretanto, sem sucesso. Agradeço toda ajuda!
# inbound connections MUST use SNC
# yyy --> SAP ROUTER DA EMPRESA QUE IRÁ ACESSAR O MEU SAP VIA SAP ROUTER.
# ECC --> SERVIDOR ECC 6
# SOL --> SERVIDOR SOLMAN
# SRM --> SERVIDOR SRM
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" YYY.YYY.YYY.YYY *
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" ECC.ECC.ECC.ECC 3200
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" ECC.ECC.ECC.ECC *
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" ECC.ECC.ECC.ECC 3300
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" ECC.ECC.ECC.ECC 3600
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" SOL.SOL.SOL.SOL 3200
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" SOL.SOL.SOL.SOL *
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" SOL.SOL.SOL.SOL 3300
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" SOL.SOL.SOL.SOL 3600
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" SRM.SRM.SRM.SRM 3600
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" SRM.SRM.SRM.SRM 3300
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" SRM.SRM.SRM.SRM *
# outbound connections to <sapservX> will use SNC --
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" YYY.YYY.YYY.YYY *
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" YYY.YYY.YYY.YYY 3200
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" YYY.YYY.YYY.YYY 3298
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" YYY.YYY.YYY.YYY 3299
# permission entries ONLY ECC
P ECC.ECC.ECC.ECC YYY.YYY.YYY.YYY 3200
P ECC.ECC.ECC.ECC YYY.YYY.YYY.YYY *
P ECC.ECC.ECC.ECC YYY.YYY.YYY.YYY 3299
P ECC.ECC.ECC.ECC YYY.YYY.YYY.YYY 3389
# all other connections will be denied
D * * *
Similar Messages
-
Configurar SAPROUTTAB para permitir acesso de fora rede interna
Bom tarde pessoal,
Gostaria de saber, como faço para configurar a rota no saprouttab para liberar o acesso externo via front end?
Ex:
O usuário na sua casa, configura o front end com o ip publico e o ip do servidor interno da organização e o mesmo terá acesso para logar no sistema remotamente.
Outra pergunta, preciso alterar o firewall interno para liberar este acesso?
Obrigado e abraços.
Denisalo Tomas,
podes me ajudar a validar o que esta a faltar aqui neste meu ficheiro razao pela qual nao cosigo me conectar de fora.
# SNC connection to and from SAP
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 194.39.131.34 *
# SNC connection to local system for R/3-Support
# R/3 Server: 192.168.1.1
# R/3 Instance: 00
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 10.1.1.15 3200
# SNC connection to local WINDOWS system for WTS, if applicable
# Windows server: 192.168.1.2
# Default WTS port: 3389
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 10.1.1.15 3389
# SNC connection to local UNIX system for SAPtelnet, if applicable
# UNIX server: 192.168.1.3
# Default Telnet port: 23
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 10.1.1.15 23
# SNC connection to local Portal system for URL access, if applicable
# Portal server: 192.168.1.4
# Port number: 50003
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 10.1.1.15 50003
# Access from the local Network to SAP
P 10.1.1.15 194.39.131.34 3299
# Permitir todas as redes temporariamente
P * * *
# deny all other connections
D * * *
Obrigado . -
Como puedo configurar photoshop par que la imagen impresa se vea igual que en el monitor?
como puedo configurar photoshop par que la imagen impresa se vea igual que en el monitor de pc
Para que la imagen en el monitor se vea "igual" que la imagen impresa (al revés de como lo planteas),
es necesario aplicar correctamente una gestión del color y crear o disponer de unos perfiles de color ICC correctos de los dispositivos.
A) Prueba de Colores
Para previsualizar en Photoshop las imágenes de forma simulada cómo quedarán impresas, (un proceso por cierto común a otras aplicaciones) hay que utilizar el comando: Vista>Prueba de Colores (View>Proof Colors).
Para ajustar esta acción hay que comprobar primero que el perfil correspondiente al dispositivo de salida esté seleccionado:
Escoger en Ver> Ajuste de Prueba (Proof Setup): A Medida (Custom). (A modo práctico se puede utilizar CMYK de trabajo si es el correcto (definido en Edición>Ajustes de Color) aunque es incompleto ya que no tiene en cuenta o simula el medio impreso, color del papel y Tinta Negra).
Escoger aqui el perfil ICC correspondiente, uno predefinido o uno creado de forma personalizada para la impresora de salida, Intento: Colorímetro relativo y marcar compensación de Punto Negro, activar tambien las dos casillas de simular Color de Papel y de Tinta Negra.
De esta forma mientras se trabaja editando imágenes en un espacio de color adecuado, en cualquier momento al activar este comando de Prueba de Colores se previsualiza o simula en pantalla una aproximación al resultado final en un determinado medio y proceso de salida. (Utilizar el atajo Cmd/Ctrl+Y alternativamente)
B) Perfil ICC de monitor.
Nada de esta funcionará si por un lado el monitor no está caracterizado y calibrado, hay que generar un perfil ICC del monitor que se utilizará en Edición>Ajustes de Color como perfil de monitor, y la iluminación alrededor del monitor es neutra, está controlada y se situa en unos parámetros según unas normas, (luz difusa diurna sin entrar en tecnicismos).
Para calibrar (con cierta frecuencia y precisión) un monitor es necesario disponer de un calibrador (espectrofotocolorimetro) que efectue estas medidas y genere el perfil ICC que caracteriza el monitor.
C) Perfil de la impresora
La impresión comercial, las imprentas, suelen utilizar o ajustarse a procesos estandarizados, que contrastan o calibran los resultados con unas normas y ajustes predefinidos, que los fabricantes suelen adecuar a normas estandard. Existen y Adobe incluye en Edición>Ajustes de Color toda una serie de perfiles ICC que representan las condiciones de impresión más comunes y utilizadas en la actualidad. Escoger por ejemplo Ajustes: Europa Prepress 3 para tomar nota de los perfiles RGB y CMYK seleccionados.
Podemos incluir aqui algunos plotter que se pueden ajustar de modo similar.
Y si la impresora o plotter es de oficina o doméstica? De chorro de tinta, cera o láser. El punto de partida podría ser un perfil genérico del modelo de impresora, pero por desgracia las variaciones entre unidades, y factores como gran variabilidad de las tintas (no sólo de marcas, sino de series, o cambios en el tiempo) incluso de la temperatura y humedad ambiental afectan o modifican el resultado. Existen dispositivos para calibrar toda clase de impresoras y servicios que basados en pruebas que se les envian para su análisis, pueden generar perfiles de cada dispositivo.
No olvidar que para mantener la uniformidad de resultados en el tiempo, es necesario mantener el sistema, medir, calibrar y aplicar esos resultados de forma perdiódica, constante.
En resumen, es necesario conocer y utilizar perfil ICC de la impresora, crear y utilizar perfil ICC del monitor, entorno (habitación, luz,...) adecuado. Y entonces cuando -simplemente- utilicemos Ver>Vista de Prueba.
Conocido como Soft Proof, el impreso es el Hard Proof.
Existen muchos libros, manuales y artículos sobre Gestion de Color, la ayuda del programa Photoshop, también explica todo esto con mayor detalle y precisión. -
Saprouter Error:Timeout while pending for route completion
Please help me with this connection troubleshoot, status of our network are as follows:
Settings:
Global IP : WW.XX.YY.ZZ --Natted to AA.BB.CC.DD
Port Open on Firewall:
SAPROUTER 3200 3299
Gateway 3300 3399
SNC Gateway 4800 4899
Host file entry for PRD R/3, BI PRD server, saprouter machine, sapserv2 on all system.
Service file entry for BI server 3601 in saprouter system is done.
SAPROUTER version 700 u2013 221
Saprouter is setup with all the environment variables set e.g: In user
variables SNC_LIB, & in system variables SECUDIR.
OSS1 setting is as per note # 33135 - Guidelines for OSS1
We are able to ping to 194.39.131.34 sapserv2 from all the system even the BI PRD server.
SAP Connection to BI server is open
Service connector is running
SAPROUTTAB:
SNC-connection from and to SAP
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 194.39.131.34 *
SNC-connection from SAP to local R/3-System for Support
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 10.0.0.18 3200
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 10.0.0.18 3201
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 10.0.0.15 3200
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" * *
#Access from the local Network to SAPNet - R/3 Frontend (OSS)
P 10.0.0.19 194.39.131.34 3299
P * 194.39.131.34 3299
P * * *
deny all other connections
D * * *
I am creating 2 part to this post as this post is getting jumbled up and making it to difficult for people to read. The second part conatins the error log from trc files.
Edited by: gab basis on Dec 24, 2009 6:45 PMErrors:
dev_rf_trc
Trace file opened at 20091224 135230 India Standard Time, SAP-REL
700,0,221 RFC-VER U 3 1090073 MT-SL
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 2517
LB: Hostname or service of the message server unknown
DEST =SAPOSS
MSHOST =/H/WW.XX.YY.ZZ /S/sapdp99/H/194.39.131.34/S/sapdp99/H/oss001
R3NAME =OSS
GROUP =EWA
ABAP Programm: RSRFCPIN (Transaction: SM59)
User: SEALBASIS (Client: 900)
Destination: SAPOSS (handle: 2, , )
dev_lg_trc
trc file: "dev_lg", trc level: 1, release: "700"
[Thr 332] Thu Dec 24 13:53:09 2009
[Thr 332] ***LOG Q0I=> NiPConnect2: connect (10060: WSAETIMEDOUT:
Connection timed out) [nixxi.cpp 2823]
[Thr 332] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 0 /
sock 1892
(SI_ECONN_REFUSE/10060; I4; ST; 116.214.28.72:3299) [nixxi.cpp
2823]
[Thr 332] *** ERROR => MsIAttachEx: NiBufConnect
to /H/WW.XX.YY.ZZ /S/sapdp99/H/194.39.131.34/S/sapdp99/H/oss001/S/sapmsO01/x failed (rc=NIEC
[Thr 332] *** ERROR => LgIAttach: MsAttach (rc=NIECONN_REFUSED)
[lgxx.c 3980]
[Thr 332] *** ERROR => LgApplSrvInfo: LgIAttach(rc=LGEMSLAYER)
[lgxx.c 1272]
[Thr 332]
[Thr 332] * ERROR partner '116.214.28.72:sapdp99' not reached
[Thr 332] *
TIME Thu Dec 24 13:53:09 2009
[Thr 332] * RELEASE 700
[Thr 332] * COMPONENT NI (network interface)
[Thr 332] * VERSION 38
[Thr 332] * RC -10
[Thr 332] * MODULE nixxi.cpp
[Thr 332] * LINE 2823
[Thr 332] * DETAIL NiPConnect2
[Thr 332] * SYSTEM CALL connect
[Thr 332] * ERRNO 10060
[Thr 332] * ERRNO TEXT WSAETIMEDOUT: Connection timed out
[Thr 332] * COUNTER 1
[Thr 332] *
[Thr 332]
Edited by: gab basis on Dec 24, 2009 6:59 PM -
Idioma español para mac? Spanish for mac?
Pues eso, he adquirido la versión en inglés para mac de Photoshop Elements 13 porque no hay opción a obtenerlo en español.
Me preguntaba si se producirá alguna actualización del software con soporte para más idiomas, o ya tendré que seguir con la versión en inglés.
I've got recently Photoshop Elements 13 for mac. It used to be any software update with support for Spanish language?Try an alternative link and validate with your 24 digit serial number - click here for PSE downloads
-
Configurar Idle para telefonos ip Cisco 7945
Hola,
Por favor si alguien me pudiera colaborar con este tema, estoy tratando de configurar una Imagen para los telefonos Cisco de la serie 7945 en el campo idle, para que despues de un tiempo de inactividad se active el logo de mi empresa por ejemplo. ya lo hice con los telefonos de la serie 7940, pero he tenido problema con los 7945, veo que el telefono llega al servidor web y hace la peticion, pero al parecer no encuentra un archivo de imagen adecuado para publicar, alguien sabe que tamaño y formato debe tener la imagen o alguien sabe los pasos para cambiar el background a todos los telefonos o configurar el Idle para la serie 7945.
Mil gracias por su valiosa colaboracion.
Saludos,No es posible cambiar el background de todos los telefonos de manera nativa con CUCM, hay varios metodos y todos ellos han sido ya discutidos previamente en CSC, solo tienes que buscar.
Si vas a preguntar en español, te recomiendo entonces lo hagas en la comunidad de dicho idioma.
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk -
Errors loading "old" PAR file to SneakPreviewSP16 for modification
I have a PAR file that was custom developed Java for iViews that was initiall developed in the SDN downloaded 3-month version of EP5 and NWDS. I then ported it to the early version of EP6 and NWDS.
In a moment of "madness", I downloaded the latest version of SAPNetweaver04SP16Preview and deleted the old version from my laptop.
Now I must make further modifications to the PAR file... but with this version of EP for NW04 and NWDS, I am getting a "laundry list" of errors trying to build the Project inside NWDS (see below). Does anyone have some suggestions on either:
(a) where to get the old download, or
(b) what jar files I am missing?
Thank you for the help.
Rich
======================== Errors from NWDS =================================
Kind Status Priority Description Resource In Folder Location
Task Not Completed Normal <?xml .project Planning line 1
Error ConnectorException cannot be resolved (or is not an exception type) for the method buildColumnVector Tools.java Planning/src.api/com/solvay/Tools line 205
Error ConnectorException cannot be resolved (or is not an exception type) for the method buildColumnVector_RMRP Tools_RMRP.java Planning/src.api/com/solvay/Tools line 67
Error ConnectorException cannot be resolved (or is not an exception type) for the method buildDataVector Tools.java Planning/src.api/com/solvay/Tools line 219
Error ConnectorException cannot be resolved (or is not an exception type) for the method fill_SELECTION_ACTSALES Tools_TransactionalData.java Planning/src.api/com/solvay/Tools line 900
Error ConnectorException cannot be resolved (or is not an exception type) for the method fillTable_TIME_SERIES Tools_MarketingForecast.java Planning/src.api/com/solvay/Tools line 378
Error ConnectorException cannot be resolved (or is not an exception type) for the method fillTable_TIME_SERIES Tools.java Planning/src.api/com/solvay/Tools line 543
Error ConnectorException cannot be resolved (or is not an exception type) for the method fillTableSelection_Long Tools_MarketingForecast.java Planning/src.api/com/solvay/Tools line 244
Error ConnectorException cannot be resolved (or is not an exception type) for the method fillTableSelection_Long_IOBJNM Tools_RMRP.java Planning/src.api/com/solvay/Tools line 231
Error ConnectorException cannot be resolved (or is not an exception type) for the method fillTableSelection_Long_IOBJNM Tools.java Planning/src.api/com/solvay/Tools line 441
Error ConnectorException cannot be resolved (or is not an exception type) for the method fillTableSelection_SAVE Tools_TransactionalData.java Planning/src.api/com/solvay/Tools line 792
Error ConnectorException cannot be resolved (or is not an exception type) for the method getKeyFigureCount Helper.java Planning/src.api/com/solvay/Common line 207
Error ConnectorException cannot be resolved (or is not an exception type) for the method inputPar_ZZ_YOZ_GETDETAIL Helper.java Planning/src.api/com/solvay/Common line 262
Error ConnectorException cannot be resolved (or is not an exception type) for the method readInput Tools_MarketingForecast.java Planning/src.api/com/solvay/Tools line 309
Error ConnectorException cannot be resolved (or is not an exception type) for the method readInputValues Tools_RMRP.java Planning/src.api/com/solvay/Tools line 83
Error ConnectorException cannot be resolved (or is not an exception type) for the method table_IT_KEY_FIGURE Helper.java Planning/src.api/com/solvay/Common line 27
Error ConnectorException cannot be resolved (or is not an exception type) for the method table_SELECTION_0 Helper.java Planning/src.api/com/solvay/Common line 38
Error ConnectorException cannot be resolved (or is not an exception type) for the method table_SELECTION_0_ADDITIONAL Tools_TransactionalData.java Planning/src.api/com/solvay/Tools line 472
Error ConnectorException cannot be resolved (or is not an exception type) for the method table_SELECTION_1 Helper.java Planning/src.api/com/solvay/Common line 105
Error ConnectorException cannot be resolved (or is not an exception type) for the method table_TIME_SERIES Helper.java Planning/src.api/com/solvay/Common line 134
Error ConnectorException cannot be resolved (or is not an exception type) for the method table02 Tools.java Planning/src.api/com/solvay/Tools line 517
Error ConnectorException cannot be resolved (or is not an exception type) for the method TD_buildColumnVector Tools_TransactionalData.java Planning/src.api/com/solvay/Tools line 106
Error ConnectorException cannot be resolved (or is not an exception type) for the method TD_buildDataVector Tools_TransactionalData.java Planning/src.api/com/solvay/Tools line 139
Error ConnectorException cannot be resolved or is not a type AM_Renderer.java Planning/src.api/com/solvay/Views/Renderer line 90
Error ConnectorException cannot be resolved or is not a type MF_Renderer.java Planning/src.api/com/solvay/Views/Renderer line 256
Error ConnectorException cannot be resolved or is not a type SF_Renderer.java Planning/src.api/com/solvay/Views/Renderer line 197
Error ConnectorException cannot be resolved or is not a type TD_Renderer.java Planning/src.api/com/solvay/Views/Renderer line 81
Error IConnection cannot be resolved (or is not a valid return type) for the method getSAPConnection Tools.java Planning/src.api/com/solvay/Tools line 61
Error IConnection cannot be resolved (or is not a valid type) for the argument client of the method execBAPIPBSRVAPS_CHANGEKEYFIGVAL_ACTSALES Tools_TransactionalData.java Planning/src.api/com/solvay/Tools line 362
Error IConnection cannot be resolved (or is not a valid type) for the argument client of the method execBAPIPBSRVAPS_CHANGEKEYFIGVAL_CURRLEVEL Tools_TransactionalData.java Planning/src.api/com/solvay/Tools line 252
Error IConnection cannot be resolved (or is not a valid type) for the argument client of the method execBAPIPBSRVAPS_CHANGEKEYFIGVAL_STOCKINTRANSIT Tools_TransactionalData.java Planning/src.api/com/solvay/Tools line 318
Error IConnection cannot be resolved (or is not a valid type) for the argument client of the method execBAPIPBSRVAPS_GETDETAIL Tools_TransactionalData.java Planning/src.api/com/solvay/Tools line 182
Error IConnection cannot be resolved (or is not a valid type) for the argument client of the method execYOZSAP_PORTALS_MACRO Tools.java Planning/src.api/com/solvay/Tools line 280
Error IConnection cannot be resolved (or is not a valid type) for the argument client of the method execYOZSAP_PORTALS_MACRO_RMRP Tools_RMRP.java Planning/src.api/com/solvay/Tools line 262
Error IConnection cannot be resolved (or is not a valid type) for the argument client of the method execYOZSAP_PORTALS_MACRO_TD Tools_TransactionalData.java Planning/src.api/com/solvay/Tools line 408
Error IConnection cannot be resolved (or is not a valid type) for the argument client of the method execZZYOZ_GETDETAIL_SAVE Tools_TransactionalData.java Planning/src.api/com/solvay/Tools line 858
Error IConnection cannot be resolved (or is not a valid type) for the argument client of the method doSaveActualSales TransactionalData.java Planning/src.api/com/solvay line 464
Error IConnection cannot be resolved (or is not a valid type) for the argument client of the method doSaveCurrInvLevel TransactionalData.java Planning/src.api/com/solvay line 434
Error IConnection cannot be resolved (or is not a valid type) for the argument client of the method doSaveStockinTransit TransactionalData.java Planning/src.api/com/solvay line 388
Error IConnection cannot be resolved (or is not a valid type) for the argument client of the method execYOZ_SAP_PORTALS_MACRO Tools_MarketingForecast.java Planning/src.api/com/solvay/Tools line 178
Error IConnection cannot be resolved (or is not a valid type) for the field Tools_AvailabilityMonitor.connection Tools_AvailabilityMonitor.java Planning/src.api/com/solvay/Tools line 24
Error IConnection cannot be resolved (or is not a valid type) for the field Tools_MarketingForecast.connection Tools_MarketingForecast.java Planning/src.api/com/solvay/Tools line 24
Error IConnection cannot be resolved (or is not a valid type) for the field Tools_MasterData.connection Tools_MasterData.java Planning/src.api/com/solvay/Tools line 18
Error IConnection cannot be resolved (or is not a valid type) for the field Tools_RMRP.connection Tools_RMRP.java Planning/src.api/com/solvay/Tools line 28
Error IConnection cannot be resolved (or is not a valid type) for the field Tools_SalesForecast.connection Tools_SalesForecast.java Planning/src.api/com/solvay/Tools line 17
Error IConnection cannot be resolved (or is not a valid type) for the field Tools_TransactionalData.connection Tools_TransactionalData.java Planning/src.api/com/solvay/Tools line 27
Error IConnection cannot be resolved (or is not a valid type) for the field Tools.connection Tools.java Planning/src.api/com/solvay/Tools line 34
Error IConnection cannot be resolved or is not a type TransactionalData.java Planning/src.api/com/solvay line 342
Error IConnection cannot be resolved or is not a type Tools_AvailabilityMonitor.java Planning/src.api/com/solvay/Tools line 60
Error IConnection cannot be resolved or is not a type Tools_MarketingForecast.java Planning/src.api/com/solvay/Tools line 121
Error IConnection cannot be resolved or is not a type Tools_MasterData.java Planning/src.api/com/solvay/Tools line 29
Error IConnection cannot be resolved or is not a type Tools_MasterData.java Planning/src.api/com/solvay/Tools line 86
Error IConnection cannot be resolved or is not a type Tools_RMRP.java Planning/src.api/com/solvay/Tools line 165
Error IConnection cannot be resolved or is not a type Tools_RMRP.java Planning/src.api/com/solvay/Tools line 264
Error IConnection cannot be resolved or is not a type Tools_TransactionalData.java Planning/src.api/com/solvay/Tools line 38
Error IConnection cannot be resolved or is not a type Tools_TransactionalData.java Planning/src.api/com/solvay/Tools line 156
Error IConnection cannot be resolved or is not a type Tools.java Planning/src.api/com/solvay/Tools line 169
Error IConnection cannot be resolved or is not a type Tools.java Planning/src.api/com/solvay/Tools line 399
Error IFunction cannot be resolved or is not a type Tools_AvailabilityMonitor.java Planning/src.api/com/solvay/Tools line 64
Error IFunction cannot be resolved or is not a type Tools_MarketingForecast.java Planning/src.api/com/solvay/Tools line 132The -resolve did not make the problems go away.
Here is the command I used to load fop.jar again:
loadjava -user cmsadmin/XXX@<hostname>:1521:TestDB -verbose -resolve -force -order -thin -grant public /export/home/fop.jar
Here is an snippet of the error messages:
ORA-29534: referenced object CMSADMIN.org/apache/fop/fo/PropertyList could n
ot be resolved
granting : execute on class org/apache/fop/fo/properties/CountryMaker to public
resolving: class org/apache/fop/fo/properties/CountryMaker
errors : class org/apache/fop/fo/properties/CountryMaker
ORA-29534: referenced object CMSADMIN.org/apache/fop/fo/PropertyList could n
ot be resolved
granting : execute on class org/apache/fop/fo/properties/LanguageMaker to public
resolving: class org/apache/fop/fo/properties/LanguageMaker
errors : class org/apache/fop/fo/properties/LanguageMaker
ORA-29534: referenced object CMSADMIN.org/apache/fop/fo/PropertyList could n
ot be resolved
granting : execute on class org/apache/fop/fo/properties/ScriptMaker to public
resolving: class org/apache/fop/fo/properties/ScriptMaker
errors : class org/apache/fop/fo/properties/ScriptMaker
ORA-29534: referenced object CMSADMIN.org/apache/fop/datatypes/ToBeImplement
edProperty$Maker could not be resolved
granting : execute on class org/apache/fop/fo/properties/HyphenateMaker to publi
c
resolving: class org/apache/fop/fo/properties/HyphenateMaker
Some classes can be loaded, others have the ORA-29534 error. Any ideas are much appreciated.
Thank you very much,
Rosi MacLean -
When I upgrade Firefox my email page does not open fully
The main menu is open but the sub menus will not
this has happened since firefox 4
I have to aninstall the revert to 3.6
Last week I asked the same question to be told that an email would be sent
NO EMAIL
(I could not open it any way)
I left my phone no 44 653 600399 but this has not resulted in any response
Do you want me to go to chrome?
Give me an answer pleaseYour old phone had a voicemail passcode; you just forgot what it was. All cell phones have voicemail passwords. Call your carrier and have them reset your voicemail account and give it a new passcode. The iPhone will remember the passcode after you enter it, so you won't have to remember it (just as you didn't with the previous phone).
-
SAProuter for Jco between Java and ABAP stack
When configuring Jco at Java only, there is an option to use SAProuter.
This is not for SMP download or OSS support.
So is there any document for this kind of SAProuter usage?
Thanks!I don't quite understand why you need SAProuter between 2 SAP instances, which means they locate in 2 different network segments and cannot communicate each other directly. But let's assume this scenario:
1. ECC in network A, IP 10.10.10.1;
2. Portal in network B, IP 192.168.1.1;
3. SAProuter has 2 adapters, IP 10.10.10.2 and 192.168.1.2.
Make sure all message server and dispatch info are maintained correctly in service file (or corresponding file on other platform) on all 3 hosts, and then when you configure Portal Jco connection routestring you need is /H/<SAProuter IP>/S/3299 to enable them communicate each other. Usually this is for security purpose of potential network attack to SAP hosts from user IP, for instance:
4. All public users in network C, IP 172...*, then you need a SAProuter which has 3 adapters.
Regards,
Effan -
Olha eu tenho um pc xp e tenho um teclado da apple com eu faço para configurar ele
e ai galera eu tenho um teclado usb e não cnsigo configurar ele para pc com dois sistema operacional xp e sevem
You shouldn't need a password to sign out of an iCloud acount in your Mac's System/iCloud preference pane:
Just clike on the Sign Out button and in the next window select the option you want: -
Saludos estimados colegas, tengo una pregunta con respecto al modulo DSC. Se que mediante este modulo puedo configurar alarmas si se superan o caen por debajo de los limites establecidos los valores especificados en variables compartidas (Hi: Enable/Lo: Enable), sin embargo noto que cuando creo una variable compartida desde un “control/indicador personalizado” (un cluster de números por ejemplo) no tengo disponible estas opciones. De hecho ni en el “NI Distributed System Manager” se pueden ver los valores de estas variables. ¿Como podría hacer para monitorear estas variables y agregar alarmas mediante el DSC?
Solved!
Go to Solution.Hola Jairo.Gutierrez.
En efecto no se pueden configurar alarmas para las variables compartidas con tipos de dato complejos (como clusters o arreglos) más que la alarma de bad status. Adicionalmente, para recuperar la información de ese trace tendrás que hacerlo programáticamente, por lo que los valores no aparecerán ni en MAX ni en el DSM, aunque si se esten guardando.
Las dos opciones que te recomiendo serían:
1. Hacer tanto el monitoreo como el loggeo de alarmas programáticamente:
a) Para el monitoreo necesitas usar los VI´s del toolkit DSC (Read Trace), decir que es un tipo de dato variante, y después convertir el variant a tu cluster.
b) Para las alarmas la única manera que se me ocurre es generar eventos a partir de los cambios de valor de la variable y compararlos programáticamente con el límite, y si lo exceden loggear una alarma de usuario que si bien no esta directamente relacionada con ese trace tu puedes saber que a eso se debe la alarma.
Para estos casos te recomiendo revisar los ejemplos del módulo DSC para que veas como manipular los traces y las alarmas programáticamente. Así puedes generar eventos a partir de cambios en las variables: https://decibel.ni.com/content/docs/DOC-4375.
La segunda opción, que es mas sencilla, es que reemplaces tu variable compartida del cluster por variables donde guardes cada uno de los elementos del cluster. Puedes usar una convención de nombres para saber que las variables pertenecen al mismo cluster, pero tendrás toda la funcionalidad del módulo DSC sin tener que hacerlo programáticamente.
Espero haya respondido tu duda.
Aldo H
Ingenieria de Aplicaciones -
Is the para duo metal case ok for iphone 5
The new Para Duo Metal case for the iphone 5 looks pretty nice and is not too expensive, but is it ok to have a metal case on this phone and not have service interruptions? Wether it be bluetooth signal, internet (wifi Signal) or cellular network connection(phone calls)? Has any one had any issues with this before?
Thank you!
Here is the link to the product:
http://www.more-thing.com/en/iphone/iphone-5/para-duo-metal-for-iphone-5.htmlWell first off, the case is not metal. It is an anodized polycarbonate plastic with a metallic finish that goes on top of a pure silicone inner case.
You do not want a case made out of metal, if nothing else it would scratch too easily and add too much weight to the phone and that's in addition to the loud clinging you'd get when you set it down.
The object of this case is to immitate metal in the most elegant way possible, and More-Thing has done just that.
The special plastic holds the finish better and gives you a lighter and more cushioned protection than real metal.
If real metal is your thing, you may want to consider a different phone, because iPhone 5 being made of aluminum and glass is pushing case makers away from metal. -
QoS for voice over access point AIR-AP1242AG-A-K9
Necesito saber si en el access point AIR-AP1242AG-A-K9 se puede configurar QoS para trafico de voz. El cliente tiene 5 laptops en las cuales tiene instalado softphones ( software de telefono IP). Desde una laptop se genera trafico de datos y voz. Gracias.
Julio,
Yes, you can do QoS on an IOS AP. The below link describes how you configure it.
http://www.cisco.com/en/US/customer/docs/wireless/access_point/12.4_21a_JA1/configuration/guide/scg12421aJA1-chap15-qos.html
Keep in mind, that with a softphone, or even dual-band cell phones, the applicaiton has to be able to mark it's traffic appropriatly, for the QoS to work as it should.
HTH,
Steve -
MaxDB backup through Backint on Oracle for TSM
Hello Gurus:
We are using TSM backint interface for Oracle database. We are in the process of implementing SCM. We would like to schedule MaxDB backup through backint interface for Oracle.
I checked some forums and configured but backint is not recognizing MaxDB parameter file. Please see below parameter file and error logs.
*BSI File:*
BACKINT D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
INPUT D:\sapdb\data\wrk\backint\sapdb.in
OUTPUT D:\sapdb\data\wrk\backint\sapdb.out
ERROROUTPUT D:\sapdb\data\wrk\backint\sapdb.err
PARAMETERFILE D:\sapdb\data\wrk\LCD\maxdb_config.par
ORIGINAL_RUNDIRECTORY L:\sapdb\LCD\sapdata
*Parameter File - MaxDB_config*
STAGING AREA: D:\TEMP\STAGE1 1024000 KB
FILES PER BACKINT CALL: 2
BACKINT: D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
PARAMETERFILE OF BACKINT: D:\oracle\SCD\102\database\initSCD.utl
HISTORY FILE: D:\sapdb\data\wrk\BackintHistory
INPUTFILE OF BACKINT: D:\sapdb\data\wrk\backint\backint.in
OUTPUTFILE OF BACKINT: D:\sapdb\data\wrk\backint\backint.out
ERRORFILE OF BACKINT: D:\sapdb\data\wrk\backint\backint.err
MAXIMAL DELAY OF BACKINT CALL: 30
Error Logs:
2010-03-30 17:38:35
Using environment variable 'TEMP' with value 'C:\Windows\TEMP' as directory for temporary files and pipes.
Using connection to Backint for MaxDB Interface.
2010-03-30 17:38:35
Checking existence and configuration of Backint for MaxDB.
Using environment variable 'BSI_ENV' with value 'D:\sapdb\data\wrk\LCD\bsi.env' as path of the configuration file of Backint for MaxDB.
Reading the Backint for MaxDB configuration file 'D:\sapdb\data\wrk\LCD\bsi.env'.
Found keyword 'BACKINT' with value 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe'.
Found keyword 'INPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.in'.
Found keyword 'OUTPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.out'.
Found keyword 'ERROROUTPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.err'.
Found keyword 'PARAMETERFILE' with value 'D:\sapdb\data\wrk\LCD\maxdb_config.par'.
Found keyword 'ORIGINAL_RUNDIRECTORY' with value 'L:\sapdb\LCD\sapdata'.
Finished reading of the Backint for MaxDB configuration file.
Using 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe' as Backint for MaxDB program.
Using 'D:\sapdb\data\wrk\backint\sapdb.in' as input file for Backint for MaxDB.
Using 'D:\sapdb\data\wrk\backint\sapdb.out' as output file for Backint for MaxDB.
Using 'D:\sapdb\data\wrk\backint\sapdb.err' as error output file for Backint for MaxDB.
Using 'D:\sapdb\data\wrk\LCD\maxdb_config.par' as parameter file for Backint for MaxDB.
Using '300' seconds as timeout for Backint for MaxDB in the case of success.
Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
Using 'L:\sapdb\LCD\sapdata\dbm.knl' as backup history of a database to migrate.
Using 'L:\sapdb\LCD\sapdata\dbm.ebf' as external backup history of a database to migrate.
Checking availability of backups using backint's inquire function.
Check passed successful.
2010-03-30 17:38:35
Checking medium.
Check passed successfully.
2010-03-30 17:38:35
Preparing backup.
Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
Setting environment variable 'BI_REQUEST' to value 'NEW'.
Setting environment variable 'BI_BACKUP' to value 'FULL'.
Constructed Backint for MaxDB call 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe -u LCD -f backup -t file -p D:\sapdb\data\wrk\LCD\maxdb_config.par -i D:\sapdb\data\wrk\backint\sapdb.in -c'.
Created temporary file 'D:\sapdb\data\wrk\backint\sapdb.out' as output for Backint for MaxDB.
Created temporary file 'D:\sapdb\data\wrk\backint\sapdb.err' as error output for Backint for MaxDB.
Writing '
.\pipe\BACKscd #PIPE' to the input file.
Prepare passed successfully.
2010-03-30 17:38:35
Starting database action for the backup.
Requesting 'SAVE DATA QUICK TO '
.\pipe\BACKscd' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'Back123'' from db-kernel.
The database is working on the request.
2010-03-30 17:38:35
Waiting until database has prepared the backup.
Asking for state of database.
2010-03-30 17:38:35 Database is still preparing the backup.
Waiting 1 second ... Done.
Asking for state of database.
2010-03-30 17:38:36 Database has finished preparation of the backup.
The database has prepared the backup successfully.
2010-03-30 17:38:36
Starting Backint for MaxDB.
Starting Backint for MaxDB process 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe -u LCD -f backup -t file -p D:\sapdb\data\wrk\LCD\maxdb_config.par -i D:\sapdb\data\wrk\backint\sapdb.in -c >>D:\sapdb\data\wrk\backint\sapdb.out 2>>D:\sapdb\data\wrk\backint\sapdb.err'.
Process was started successfully.
Backint for MaxDB has been started successfully.
2010-03-30 17:38:36
Waiting for end of the backup operation.
2010-03-30 17:38:36 The backup tool process has finished work with return code 2.
2010-03-30 17:38:36 The backup tool is not running.
2010-03-30 17:38:36 The database is working on the request.
2010-03-30 17:38:36 The database is working on the request.
2010-03-30 17:38:41 The database is working on the request.
2010-03-30 17:38:51 The database is working on the request.
2010-03-30 17:39:06 The database is working on the request.
2010-03-30 17:39:26 The database is working on the request.
2010-03-30 17:39:37 Canceling Utility-task after a timeout of 60 seconds elapsed ... OK.
2010-03-30 17:39:38 The database has finished work on the request.
Receiving a reply from the database kernel.
Got the following reply from db-kernel:
SQL-Code :-903
The backup operation has ended.
2010-03-30 17:39:38
Filling reply buffer.
Have encountered error -24920:
The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
Constructed the following reply:
ERR
-24920,ERR_BACKUPOP: backup operation was unsuccessful
The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
Reply buffer filled.
2010-03-30 17:39:38
Cleaning up.
Copying output of Backint for MaxDB to this file.
**-- Begin of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)--**
**Data Protection for SAP(R)**
**Interface between BRTools and Tivoli Storage Manager***
**- Version 6, Release 1, Modification 0.0 for Win x64 -**
**Build: 358 compiled on Nov 4 2008**
**(c) Copyright IBM Corporation, 1996, 2008, All Rights Reserved.**
**BKI8310E: The keyword MAXIMAL is not allowed.**
**BKI1001E: syntax error in file 'D:\sapdb\data\wrk\LCD\maxdb_config.par'. Exiting program.**
**BKI0020I: End of program at: 03/30/10 17:38:36 .**
**BKI0021I: Elapsed time: 00 sec .**
**BKI0024I: Return code is: 2.**
End of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)----
Removed Backint for MaxDB's temporary output file 'D:\sapdb\data\wrk\backint\sapdb.out'.
Copying error output of Backint for MaxDB to this file.
Begin of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
End of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
Removed Backint for MaxDB's temporary error output file 'D:\sapdb\data\wrk\backint\sapdb.err'.
Removed the Backint for MaxDB input file 'D:\sapdb\data\wrk\backint\sapdb.in'.
Have finished clean up successfully.
Any help will be appreciated.
Thanks,
Miral.> We are using TSM backint interface for Oracle database. We are in the process of implementing SCM. We would like to schedule MaxDB backup through backint interface for Oracle.
> *BSI File:*
>
> BACKINT D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
> *Parameter File - MaxDB_config*
> STAGING AREA: D:\TEMP\STAGE1 1024000 KB
> FILES PER BACKINT CALL: 2
> BACKINT: D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
>
> Using 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe' as Backint for MaxDB program.
> 2010-03-30 17:39:38
> Cleaning up.
> Copying output of Backint for MaxDB to this file.
> **Data Protection for SAP(R)**
> **Interface between BRTools and Tivoli Storage Manager***
> **- Version 6, Release 1, Modification 0.0 for Win x64 -**
> **BKI8310E: The keyword MAXIMAL is not allowed.**
> **BKI1001E: syntax error in file 'D:\sapdb\data\wrk\LCD\maxdb_config.par'. Exiting program.**
> **BKI0020I: End of program at: 03/30/10 17:38:36 .**
> **BKI0021I: Elapsed time: 00 sec .**
> **BKI0024I: Return code is: 2.**
>
> -
End of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)----
> Removed Backint for MaxDB's temporary output file 'D:\sapdb\data\wrk\backint\sapdb.out'.
> Copying error output of Backint for MaxDB to this file.
> -
Begin of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
@Markus: thanks for the hint with the quote-formatting option!
Concerning the issue:
Sorry, but you misunderstood the way how the general BACKINT for Oracle interface is used with MaxDB.
See, MaxDB comes with a own BACKINT executable.
This is a enhanced BACKINT tools that allows pipes as data input channels - which is not supported by the Backint for Oracle.
The MaxDB Backint serves as a adapter program between the MaxDB Kernel and the backint for Oracle program.
So instead of
BACKINT: D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
you should point it to the MaxDB provided adapater program.
I propose to revisit the documentation on that topic [Connecting to a Backint for Oracle Interface |http://maxdb.sap.com/doc/7_7/45/746a5712e14022e10000000a1553f6/content.htm].
best regards,
Lars -
Error BACKINT for Oracle Connection
hi @ maxdb gurus...
i have a problem backing up my maxdb 7.6.0.033 (serving for a mysap.erp2005 on aix 5.3) using the backint mechanism.
-> backup media created: two pipes and one parallel medium containing these pipes
-> bsi.env has been created
-> backint4sapdb.sar contains
4 staging areas each with 4096 MB
files per backint call 2
-> maxdb is about 57 gb perm. data area (and 6 gb temp.)
i use the backup wizard (dbmgui) to invoke a complete data backup which starts (pipes are created in the file system) and runs until approx. 4 gb...then the backup terminates with error "-24920 backup operation was unsuccesful. The database request failed with error -8020"
what might be the problem? are the staging areas too small? is says that when using only one stage area it must hold the complete database...can i then conclude that 4 staging areas must hold the database as well - meaning they must be around 15 gb each?
GreetZ, AHyup...but that also means that the sum of the staging areas need as much space as the database ie. around 70 gigs netto! the staging files will be filled and thus grow until the defined size, meaning that the file system(s) need to be big enough!
everything works fine until the stage files are filled (up to the defined size) and then stops...when i change the sizes of the staging areas i can reproduce the error!
i compared the tsm implementation of that system with another system (live cache...kind of small regarding db size...) and found nothing serious...
-> dbm.ebp (AIX 5.3, MaxDB 7.6.0.033, ERP2005, TSM 5.3.3.0)
2006-11-09 13:56:50
Using environment variable 'TEMP' with value '' as directory for temporary files and pipes.
Using environment variable 'TMP' with value '' as directory for temporary files and pipes.
Using connection to Backint for MaxDB Interface.
2006-11-09 13:56:50
Checking existence and configuration of Backint for MaxDB.
Using configuration variable 'BSI_ENV' = '/sapdb/data/wrk/TDV/bsi.env' as path of the configuration file of Backint for MaxDB.
Setting environment variable 'BSI_ENV' for the path of the configuration file of Backint for MaxDB from '/sapdba/data/wrk/TDV/bsi.env' to configuration value '/sapdb/data/wrk/TDV/bsi.env'.
Reading the Backint for MaxDB configuration file '/sapdb/data/wrk/TDV/bsi.env'.
The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
Found keyword 'BACKINT' with value '/sapdb/TDV/db/bin/backint'.
The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
Found keyword 'INPUT' with value '/sapdb/TDV/backup/backint4sapdb.in'.
Found keyword 'OUTPUT' with value '/sapdb/TDV/backup/backint4sapdb.out'.
Found keyword 'ERROROUTPUT' with value '/sapdb/TDV/backup/backint4sapdb.err'.
The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
Found keyword 'PARAMETERFILE' with value '/sapdb/data/wrk/TDV/backint4sapdb.par'.
Found keyword 'TIMEOUT_SUCCESS' with value '6000'.
Found keyword 'TIMEOUT_FAILURE' with value '300'.
Finished reading of the Backint for MaxDB configuration file.
Using '/sapdb/TDV/db/bin/backint' as Backint for MaxDB program.
Using '/sapdb/TDV/backup/backint4sapdb.in' as input file for Backint for MaxDB.
Using '/sapdb/TDV/backup/backint4sapdb.out' as output file for Backint for MaxDB.
Using '/sapdb/TDV/backup/backint4sapdb.err' as error output file for Backint for MaxDB.
Using '/sapdb/data/wrk/TDV/backint4sapdb.par' as parameter file for Backint for MaxDB.
Using '6000' seconds as timeout for Backint for MaxDB in the case of success.
Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
Using '/sapdb/data/wrk/TDV/dbm.knl' as backup history of a database to migrate.
Using '/sapdb/data/wrk/TDV/dbm.ebf' as external backup history of a database to migrate.
Checking availability of backups using backint's inquire function.
Check passed successful.
2006-11-09 13:56:50
Checking medium.
Check passed successfully.
2006-11-09 13:56:50
Preparing backup.
Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
Setting environment variable 'BI_REQUEST' to value 'NEW'.
Setting environment variable 'BI_BACKUP' to value 'FULL'.
Constructed Backint for MaxDB call '/sapdb/TDV/db/bin/backint -u TDV -f backup -t file -p /sapdb/data/wrk/TDV/backint4sapdb.par -i /sapdb/TDV/backup/backint4sapdb.in -c'.
Created temporary file '/sapdb/TDV/backup/backint4sapdb.out' as output for Backint for MaxDB.
Created temporary file '/sapdb/TDV/backup/backint4sapdb.err' as error output for Backint for MaxDB.
Writing '/sapdb/TDV/backup/back-tdv-data-m10.pipe #PIPE' to the input file.
Writing '/sapdb/TDV/backup/back-tdv-data-m11.pipe #PIPE' to the input file.
Prepare passed successfully.
2006-11-09 13:56:51
Creating pipes for data transfer.
Creating pipe '/sapdb/TDV/backup/back-tdv-data-m10.pipe' ... Done.
Creating pipe '/sapdb/TDV/backup/back-tdv-data-m11.pipe' ... Done.
All data transfer pipes have been created.
2006-11-09 13:56:51
Starting database action for the backup.
Requesting 'SAVE DATA QUICK TO '/sapdb/TDV/backup/back-tdv-data-m10.pipe' PIPE,'/sapdb/TDV/backup/back-tdv-data-m11.pipe' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BACK-TDV-DATA-G1'' from db-kernel.
The database is working on the request.
2006-11-09 13:56:51
Waiting until database has prepared the backup.
Asking for state of database.
2006-11-09 13:56:51 Database is still preparing the backup.
Waiting 1 second ... Done.
Asking for state of database.
2006-11-09 13:56:52 Database is still preparing the backup.
Waiting 2 seconds ... Done.
Asking for state of database.
2006-11-09 13:56:54 Database is still preparing the backup.
Waiting 3 seconds ... Done.
Asking for state of database.
2006-11-09 13:56:57 Database is still preparing the backup.
Waiting 4 seconds ... Done.
Asking for state of database.
2006-11-09 13:57:01 Database is still preparing the backup.
Waiting 5 seconds ... Done.
Asking for state of database.
2006-11-09 13:57:06 Database has finished preparation of the backup.
The database has prepared the backup successfully.
2006-11-09 13:57:06
Starting Backint for MaxDB.
Starting Backint for MaxDB process '/sapdb/TDV/db/bin/backint -u TDV -f backup -t file -p /sapdb/data/wrk/TDV/backint4sapdb.par -i /sapdb/TDV/backup/backint4sapdb.in -c >>/sapdb/TDV/backup/backint4sapdb.out 2>>/sapdb/TDV/backup/backint4sapdb.err'.
Process was started successfully.
Backint for MaxDB has been started successfully.
2006-11-09 13:57:06
Waiting for end of the backup operation.
2006-11-09 13:57:06 The backup tool is running.
2006-11-09 13:57:06 The database is working on the request.
2006-11-09 13:57:11 The backup tool is running.
2006-11-09 13:57:11 The database is working on the request.
2006-11-09 13:57:21 The backup tool is running.
2006-11-09 13:57:21 The database is working on the request.
2006-11-09 13:57:36 The backup tool is running.
2006-11-09 13:57:36 The database is working on the request.
2006-11-09 13:57:56 The backup tool is running.
2006-11-09 13:57:56 The database is working on the request.
2006-11-09 13:58:21 The backup tool is running.
2006-11-09 13:58:21 The database is working on the request.
2006-11-09 13:58:51 The backup tool is running.
2006-11-09 13:58:51 The database is working on the request.
2006-11-09 13:59:21 The database has finished work on the request.
Receiving a reply from the database kernel.
Got the following reply from db-kernel:
SQL-Code :-8020
Date :20061109
Time :00135703
Database :TDV
Server :r4335
KernelVersion :Kernel 7.6.00 Build 033-123-130-873
PagesTransfered :377688
PagesLeft :6903331
MediaName :BACK-TDV-DATA-G1
Location :/sapdb/TDV/backup/back-tdv-data-m10.pipe
Errortext :end of file
Label :DAT_000000017
IsConsistent :true
FirstLogPageNo :247812
DBStamp1Date :20061109
DBStamp1Time :00135651
BDPageCount :7280971
DevicesUsed :2
DatabaseID :r4335:TDV_20061109_135703
Max Used Data Page :0
Converter Page Count :5201
2006-11-09 13:59:21 The backup tool is running.
2006-11-09 13:59:22 The backup tool process has finished work with return code 2.
2006-11-09 13:59:22 The backup tool is not running.
The backup operation has ended.
2006-11-09 13:59:22
Filling reply buffer.
Have encountered error -24920:
The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
Constructed the following reply:
ERR
-24920,ERR_BACKUPOP: backup operation was unsuccessful
The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
Reply buffer filled.
2006-11-09 13:59:22
Cleaning up.
Removing data transfer pipes.
Removing data transfer pipe /sapdb/TDV/backup/back-tdv-data-m11.pipe ... Done.
Removing data transfer pipe /sapdb/TDV/backup/back-tdv-data-m10.pipe ... Done.
Removed data transfer pipes successfully.
Copying output of Backint for MaxDB to this file.
---------- Begin of output of Backint for MaxDB (/sapdb/TDV/backup/backint4sapdb.out)----------
Reading parameter file /sapdb/data/wrk/TDV/backint4sapdb.par.
Using staging area /sapdb/TDV/backup/stage1 with a size of 1585446912 bytes.
Using staging area /sapdb/TDV/backup/stage2 with a size of 1585446912 bytes.
Using 1 file per Backint for Oracle call.
Using /sapdb/TDV/dbs/backint as Backint for Oracle.
Using /sapdb/TDV/dbs/initTDV.utl as parameterfile of Backint for Oracle.
Using /sapdb/data/wrk/TDV/backint4oracle.his as history file.
Using /sapdb/TDV/backup/backint4oracle.in as input of Backint for Oracle.
Using /sapdb/TDV/backup/backint4oracle.out as output of Backint for Oracle.
Using /sapdb/TDV/backup/backint4oracle.err as error output of Backint for Oracle.
Using a maximal delay for a Backint for Oracle call of 60 seconds.
Reading input file /sapdb/TDV/backup/backint4sapdb.in.
Backing up pipe /sapdb/TDV/backup/back-tdv-data-m10.pipe.
Backing up pipe /sapdb/TDV/backup/back-tdv-data-m11.pipe.
Found 2 entries in the input file.
Starting the backup.
Starting pipe2file program(s).
Waiting for creation of temporary files.
1 temporary file is available for backup.
Calling Backint for Oracle at 2006-11-09 13:59:20.
Calling '/sapdb/TDV/dbs/backint -u TDV -f backup -t file -p /sapdb/TDV/dbs/initTDV.utl -i /sapdb/TDV/backup/backint4oracle.in -c' .
Backint for Oracle ended at 2006-11-09 13:59:20 with return code 2.
Backint for Oracle output:
Backint for Oracle output: Data Protection for mySAP(R)
Backint for Oracle output:
Backint for Oracle output: Interface between BR*Tools and Tivoli Storage Manager
Backint for Oracle output: - Version 5, Release 3, Modification 2.0 for AIX LF 64-bit -
Backint for Oracle output: Build: 275 compiled on Nov 20 2005
Backint for Oracle output: (c) Copyright IBM Corporation, 1996, 2005, All Rights Reserved.
Backint for Oracle output:
Backint for Oracle output: BKI2027I: Using TSM-API version 5.3.3.0 (compiled with 5.3.0.0).
Backint for Oracle output: BKI2000I: Successfully connected to ProLE on port tdpr3ora64.
Backint for Oracle output: BKI0005I: Start of program at: Thu Nov 9 13:59:20 MEZ 2006 .
Backint for Oracle output: BKI5014E: Tivoli Storage Manager Error:
Backint for Oracle output: ANS1035S (RC406) Options file '*' could not be found.
Backint for Oracle output:
Backint for Oracle output: BKI0020I: End of program at: Thu Nov 9 13:59:20 MEZ 2006 .
Backint for Oracle output: BKI0021I: Elapsed time: 00 sec .
Backint for Oracle output: BKI0024I: Return code is: 2.
Backint for Oracle output:
Backint for Oracle error output:
Finished the backup unsuccessfully.
#ERROR /sapdb/TDV/backup/back-tdv-data-m10.pipe
#ERROR /sapdb/TDV/backup/back-tdv-data-m11.pipe
---------- End of output of Backint for MaxDB (/sapdb/TDV/backup/backint4sapdb.out)----------
Removed Backint for MaxDB's temporary output file '/sapdb/TDV/backup/backint4sapdb.out'.
Copying error output of Backint for MaxDB to this file.
---------- Begin of error output of Backint for MaxDB (/sapdb/TDV/backup/backint4sapdb.err)----------
Backint for Oracle was unsuccessful.
---------- End of error output of Backint for MaxDB (/sapdb/TDV/backup/backint4sapdb.err)----------
Removed Backint for MaxDB's temporary error output file '/sapdb/TDV/backup/backint4sapdb.err'.
Removed the Backint for MaxDB input file '/sapdb/TDV/backup/backint4sapdb.in'.
Have finished clean up successfully.
i invoke the backup through dbmgui, not dbmcli!
any clues? thx in advance!
GreetZ, AH
Maybe you are looking for
-
Hi, I am trying to include RSS Feeds in my Team site. But i am not able to do so and i get the error message like "The requested RSS feed could not be displayed. Please verify the settings and url for this feed. If this problem persists, please conta
-
The sort field is not used when ordering multiple cds in one alumn folder, how do I correct this?
It is using the track number and not the sort order field. The reason I have multiple cds in one alumn is because they are books on cd.
-
5400 / 7200 RPM. How To Check That?
hi guys. the box with a brand new external usb drive i am planning to purchase from my local computer store doesn't say whether it's as fast as 5400 or 7200 rpm. how do i normally check that parameter through my computer? i tried checking that on my
-
2 day old MBP not running off AC adapter.
My two day old MBP is refusing to tun off of the charger. Yesterday I had no problems with it, But now when I plug in the magsafe the light doesn't come on or anything. Twice I have switched the power outlet that the charger was plugged into and it w
-
Hi. For awhile now my quicktime visuals have been totally messed up. Whenever I open a video using quicktime, the audio is fine, but all I see for the visual is a turquoise colored blur. I updated quicktime to the newest version but it still doesn't