Blog Karma-IT

Hay un bug de la aplicación ping en Red hat haciendo que cuando se ejecuta devuelve una ip diferente al que devuelve nslookup. El caso está documentado en el siguiente enlace :

https://access.redhat.com/solutions/4542771

Ping resolves a different IP than what is returned by nslookup. - Red
When attempting to ping by hostname it is pinging an address different from what is returned by nslookup

nscd -i hosts

 
Ping resolves a different IP than what is returned by nslookup.
SOLUTION VERIFIED - Updated October 30 2019 at 8:24 PM -
English
Environment
Red Hat Enterprise Linux
Issue
When attempting to ping by hostname it is pinging an address different from what is returned by nslookup
Resolution
ï	Clear the nscd hosts db
Raw
 
# nscd -i hosts
 
 
Root Cause
The entry for the host in /var/db/ncsd/hosts was not correct. glibc will check the entry for the host in /var/db/ncsd/hosts via /var/run/nscd/socket before referencing /etc/nsswitch.conf.
Snip from an strace of a ping
Raw
 
23237 11:45:36.523725 socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5<UNIX:[1814099]> <0.000008>
23237 11:45:36.523797 connect(5<UNIX:[1814099]>, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory) <0.000012>
23237 11:45:36.523865 close(5<UNIX:[1814099]>) = 0 <0.000008>
23237 11:45:36.523916 socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5<UNIX:[1814100]> <0.000005>
23237 11:45:36.523960 connect(5<UNIX:[1814100]>, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory) <0.000008>
23237 11:45:36.524014 close(5<UNIX:[1814100]>) = 0 <0.000005>
23237 11:45:36.524068 open("/etc/nsswitch.conf", O_RDONLY|O_CLOEXEC) = 5</etc/nsswitch.conf> <0.000007>
23237 11:45:36.524107 fstat(5</etc/nsswitch.conf>, {st_dev=makedev(253, 1), st_ino=526196, st_mode=S_IFREG|0644, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=8, st_size=1768, st_atime=1572435989 /* 2019-10-30T07:46:29.194508306-0400 */, st_atime_nsec=194508306, st_mtime=1544905437 /* 2018-12-15T15:23:57.226889025-0500 */, st_mtime_nsec=226889025, st_ctime=1544905437 /* 2018-12-15T15:23:57.226889025-0500 */, st_ctime_nsec=226889025}) = 0 <0.000005>
23237 11:45:36.524154 read(5</etc/nsswitch.conf>, "#\n# /etc/nsswitch.conf\n#\n# An example Name Service Switch config file. This file should be\n# sorted with the most-used services at the beginning.\n#\n# The entry '[NOTFOUND=return]' means that the search for an\n# entry should stop if the search in the previous entry turned\n# up nothing. Note that if the search failed due to some other reason\n# (like no NIS server responding) then the search continues with the\n# next entry.\n#\n# Valid entries include:\n#\n#\tnisplus\t\t\tUse NIS+ (NIS version 3)\n#\tnis\t\t\tUse NIS (NIS version 2), also called YP\n#\tdns\t\t\tUse DNS (Domain Name Service)\n#\tfiles\t\t\tUse the local files\n#\tdb\t\t\tUse the local database (.db) files\n#\tcompat\t\t\tUse NIS on compat mode\n#\thesiod\t\t\tUse Hesiod for user lookups\n#\t[NOTFOUND=return]\tStop searching if not found so far\n#\n\n# To use db, put the \"db\" in front of \"files\" for entries you want to be\n# looked up first in the databases\n#\n# Example:\n#passwd:    db files nisplus nis\n#shadow:    db files nisplus nis\n#group:     db files nisplus nis\n\npasswd:      files sss systemd\nshadow:     files sss\ngroup:       files sss systemd\n\n#hosts:     db files nisplus nis dns\nhosts:      files mdns4_minimal [NOTFOUND=return] dns myhostname mymachines\n\n# Example - obey only what nisplus tells us...\n#services:   nisplus [NOTFOUND=return] files\n#networks:   nisplus [NOTFOUND=return] files\n#protocols:  nisplus [NOTFOUND=return] files\n#rpc:        nisplus [NOTFOUND=return] files\n#ethers:     nisplus [NOTFOUND=return] files\n#netmasks:   nisplus [NOTFOUND=return] files\n\nbootparams: nisplus [NOTFOUND=return] files\n\nethers:     files\nnetmasks:   files\nnetworks:   files\nprotocols:  files\nrpc:        files\nservices:   files sss\n\nnetgroup:   files sss\n\npublickey:  nisplus\n\nautomount:  files sss\naliases:    files nisplus\n", 4096) = 1768 <0.000005>
23237 11:45:36.524203 read(5</etc/nsswitch.conf>, "", 4096) = 0 <0.000005>
23237 11:45:36.524231 close(5</etc/nsswitch.conf>) = 0 <0.000005>
 
 
Diagnostic Steps
ï	Confirm the IP returned by nslookup
Raw
 
[testbuild root @ test ~]
# nslookup test.example.com
Server:         192.168.0.65
Address:        192.168.0.65#53

Non-authoritative answer:
Name:   test.example.com
Address: 192.168.0.182
 
 
ï	Check ip used by ping
Raw
 
[testbuild root @ test ~]
# ping test.example.com
PING test.example.com (192.168.0.118) 56(84) bytes of data.
From 192.168.0.123 (192.168.0.123) icmp_seq=1 Destination Host Unreachable
From 192.168.0.123 (192.168.0.123) icmp_seq=2 Destination Host Unreachable
^C
--- test.example.com ping statistics ---
2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1001ms
 
 
ï	Check /etc/hosts to make sure there is no entry pointing to the wrong IP
Raw
 
# cat etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1       localhost.localdomain localhost
::1     localhost6.localdomain6 localhost6
 
 
ï	confirm if ncsd is configured to cache hosts
Raw
 
# cat /etc/nscd.conf
----------snip----------
        enable-cache            hosts           yes
        positive-time-to-live   hosts           3600
        negative-time-to-live   hosts           20
        suggested-size          hosts           211
        check-files             hosts           yes
        persistent              hosts           yes
        shared                  hosts           yes
        max-db-size             hosts           33554432
---------snip------------
 
 
ï	Product(s)
ï	Red Hat Enterprise Linux
ï	Category
ï	Configure
ï	Tags
ï	nscd
This solution is part of Red Hatís fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Ping resolves a different IP than what is returned by nslookup. - Red
When attempting to ping by hostname it is pinging an address different from what is returned by nslookup

Background jobs are scheduled for programs which usually take longer to complete. Many times the background job ends up with some error which can only be generated by a background job, and to find out the root cause debugging background job is necessary.

You can debug background jobs, when they are active, finished or in a cancelled state.

If you want to debug a job which is already completed then it will replicate the same run in debug mode.

To debug a background job you can follow steps below:

■ Goto SM37 and select Job

■ Enter JDBG in ok command box

■ Press Enter

This will trigger the job in debug mode. And will perform the same task it has earlier.

1. En primer lugar, debemos asegurarnos de que la versión deseada del kernel de SAP sea
   compatible con la versión existente del kernel del sistema operativo y las versiones de productos SAP con
   la ayuda de la matriz de disponibilidad de productos (PAM).
2. Después de decidir la versión del kernel de destino, descargue la base de datos independiente, DB
   archivos dependientes (SAPEXE_..SAR y SAPEXEDB_..SAR) y colocar
   ellos en el servidor.
3. Cree un directorio en el servidor con el siguiente comando.
   mkdir nuevo núcleo
4. Copie los archivos dependientes de la base de datos e independientes de la base de datos en el archivo recién creado.
   directorio.

cp –pr SAPEXE_..SAR SAPEXEDB_..SAR /nuevokernel

5. Extraiga los archivos utilizando el ejecutable SAPCAR. (Se puede descargar explícitamente o
   se puede utilizar el existente en el servidor).

./SAPCAR.EXE –xvf SAPEXE_..SAR
./SAPCAR.EXE –xvf SAPEXEDB_..SAR

6. Una vez extraídos los archivos, asigne la autorización y los permisos adecuados para
   el ejecutable.

chown –R adm:sapsys *
chmod –R 755 *

7. Ahora detenga los servicios de la aplicación y asegúrese de que no haya procesos.
   ejecutándose con el usuario adm.
8. Realice una copia de seguridad coherente del directorio global. (Asegúrese de tomar el
   copia de seguridad del directorio global como las copias de seguridad realizadas en los directorios locales
   sería sobrescrito por el kernel en el directorio global durante el inicio de la aplicación y en tales casos no será posible revertir el kernel).
9. Copie el kernel recién extraído al directorio global desde la ruta extraída.
   cp –pr * /sapmnt//exe/uc/linuxx86_64
10. Una vez copiado el kernel, verifique la versión del kernel usando el ejecutable.
    “disp+trabajo”.
11. Ejecute el comando ./saproot.sh con el usuario root desde el directorio global. (Este comando
    asigna la propiedad y los permisos deseados al ejecutable, como br**,
    sapuxusrechk, icmbnd, etc.).
12. Una vez realizadas las comprobaciones podemos iniciar la instancia de SAP.
13. La instancia de SAP copia el kernel desde los puntos de montaje globales al local.
    puntos de montaje y directorios de aplicaciones utilizando el programa back-end “sapcpe” para
    todos los servidores de aplicaciones.
14. Una vez que la instancia esté en funcionamiento, valide la versión del kernel desde el
    capa de aplicación también.

Se trata de un copiloto de IA generativa en lenguaje natural, con el que pretende que los usuarios SAP formulen sus preguntas directamente en el chat y les responda con soluciones contextualizadas basadas en una amplia BD de datos.

Prometen que con este IA los trabajadores harán su trabajo de una forma más:
rápida, inteligente, con mejores resultados y con control total de las decisiones ->run smarter, run faster,  run better.

 “Joule comprenderá lo que quieres decir, no solo lo que dices”, dijo el CEO de SAP SE, Christian Klein.

Joule estará disponible con SAP SuccessFactors y SAP Start en noviembre de este año, y con SAP S/4HANA Cloud Public Edition a principios del próximo año. Le seguirán SAP Customer Experience y SAP Ariba, junto con SAP Business Technology Platform, así como muchas otras actualizaciones
 en toda la cartera de SAP que se anunciarán en los diferentes eventos que la compañía irá celebrando entre octubre y noviembre de este año.

https://www.sap.com/products/artificial-intelligence/ai-assistant.html

Ya sabemos que a finales de 2027 los productos basados en Business suite o Netweaver van a ir quedando fuera de mantenimiento y con la aparición de la plataforma S4HANA todo se vuelve menos personalizable. Solo hay que ver la apuesta de SAP en el offering de servicios cloud como RISE, en el que se deja de tener la propiedad de todo el producto y se basa en ser dueño de los datos.

La noticia es que a finales de julio dejaron de estar vigentes las certificaciones de desarrollador ABAP NetWeaver C_TAW12 y C_S4HDEV

Puede parecer que SAP no quiere que haya programadores que hagan sus “Zetas”, sino que se estan adaptando a las nuevas tecnologias cloud. Tiene todo el sentido, si la dirección es mantener un software administrado por SAP, se programe las necesidades de los clientes en la tecnologia SAP BTP.

El nuevo modelo es ABAP Platform y puedes ver el itinerario en SAP Leaning en el que introducen a programar en ABAP Cloud ( SAP BTP, ABAP environment ) si, si, esto es desarrollar aplicaciones ABAP en un modelo RESTful Application Programming.

Pues si no teniais nada que hacer este verano ya podéis descargar la plataforma trial y empezar a desarrollar en ABAP Cloud.

Buenas vacaciones 🙂

En el SWPM podemos pasarle diferentes opciones al llamarlo por comandos. Si queremos ver todas esas opciones solo tenemos de escribir ./sapinst -p

Example :- ./sapinst -p

Available options

> Sapinst :-

[root@<USERNAME> SWPM]# ./sapinst -p [==============================] / extracting… done!

== This will start the list ==

SAPinst properties: =====================

  •SAPINST_CONTROL_URL:

points to a control(control.xml) or a catalog(product.catalog) file.

•SAPINST_CWD:

directory that SAPinst should use as its working directory (works only if  SAPinst has write permissions in that directory) •GUISERVER_DIALOG_PORT:

the port for communication of the GUI Server with the GUI  default: 21212

•SAPINST_MESSAGE_CONSOLE_THRESHOLD:

trace level console  values: flow_trace, trace, info, phase, warning, error, external(for ACC);  default: error

•SAPINST_MESSAGE_DEVLOG_THRESHOLD(sapinst_dev.log):

trace level developer log file  values: flow_trace, trace, info, phase, warning, error  default: flow_trace

•SAPINST_JSLIB_TRACE:

switch to activate the JS trace functionality for specific JS classes;  value: comma separated list of JS classes or all  default: empty  if the value contains ‘flow_trace’ and ‘Retry’ is pressed then the  framework activates flow trace

•SAPINST_RFCLIB_TRACE:

switch to enable traces for RFC calls issued by SAPinst  attention: setting this variable to true may cause  passwords to appear in clear text in log files;  default: false •SAPINST_MSLIB_TRACE:

determines trace level of kernel trace library  allowed values: 0-3  default: 1

•SAPINST_PACKAGES_URL:

path and name of CD names and labels file

•SAPINST_SAVE_INPUT:

after each dialog step write user input to keydb file if a dialog was  displayed; default: false

•SAPINST_SKIP_DIALOGS:

skip all the installation dialogs?; default: false

•SAPINST_SKIP_ERRORSTEP:

skip the first step whose status is ERROR; set the step status to OK;  default: false

•SAPINST_START_GUI:

automatically start the GUI; default: true

•SAPINST_START_GUISERVER:

automatically start the GUI Server; default: true

•SAPINST_TOPLEVEL_URL:

name of file which is used to override the top-level components in the control  file

•SAPINST_RESOURCE_URL:

path and name of file which contains F1 help used during the installation

•SAPINST_USE_HOSTNAME:

framework will return the value of that property in case of calling the  getHostName() function (value will not be checked)

•SAPINST_PARAMETER_CONTAINER_URL:

framework will use that keydb container for reading initial values for the  instance parameters

•SAPINST_EXECUTE_PRODUCT_ID:

if the SAPinst is starting using a product.catalog file this value is used to  select the service to be installed (attribute ID at the component tag);  if no product exists with that ID the product selection dialog will be shown

•SAPINST_INIFILE_MODE:

define the handling of the ini file parameter  values:  ignore do not read parameter from file but write them  after dialog phase  default values (default) read parameter from file and use them as defaults  final same as default values, in addition set the parameters to not  changeable and tag them with  GUIENG_USER_INPUT=GUIENG_TRUE, that means if each  parameter on a dialog is tagged with that  property, the dialog isn’t shown

•SAPINST_STOP_AFTER_DIALOG_PHASE:

values:  true stops the execution after processing all dialog steps  false (default) go on with doing phase after dialog phase

•SAPINST_LABEL_IDX_URL:

path to directory which contains LABELIDX.ASC or LABEL.ASC file

•SAPINST_SLIDE_SHOW_URL:

path and name of file which contains images shown in a slide show during the  doing phase

•SAPINST_JVM_PROPERTIES

Property file for the framework JVM usage. Default: jvmUsage.properties

•SAPINST_GUI_ACCESSIBLE:

run GUI in accessibility mode, requires additional software/hardware  default: false

•JCE_POLICY_ZIP

This property is obsolete and not supported any more.

•SAPINST_REMOTE_ACCESS_USER

name of an OS user which may logon remotely (with name and password). See also SAP Note 1745524.  default: name and password of the SAPinst process owner are needed

•SAPINST_REMOTE_ACCESS_USER_IS_TRUSTED

enables or disables warning concerning remote access user: this user has to be a trusted user. See also SAP Note 1745524.  default: false •SAPINST_AUTHENTICATION_UNLIMITED

true set user and password field length of the remote dialog to unlimited.  false (default)

•SAPINST_INPUT_PARAMETERS_URL:

points to a text file containing key=value pairs. If the SAPINST_INPUT_PARAMETERS_URL is defined and a component gets processed the first time  SAPInst is checking for each component parameter the existence of attribute defval-for-inifile-generation.  If an attribute is specified SAPinst is using the attribute value as a key for the search within the SAPINST_INPUT_PARAMETERS_URL key/value pairs.  If SAPinst can find a key matching to the attribute value it is setting the component parameter to the corresponding value.

•SAPINST_SDT_USER:

This property is obsolete and not supported any more.

•SAPINST_SDT_PASSWORD:

This property is obsolete and not supported any more.

•GUISERVER_HTTP_PORT:

This property is obsolete and not supported any more.

•SAPINST_JRE_HOME:

path to external SAP Java Runtime Environment (JRE). E.g. /usr/sap/jvm6138/jre

•SAPINST_HTTP_PORT:

HTTP port of SAPinst. Used for sending feedback to SAP.

•SAPINST_SEND_ANALYTICS:

If true, dialog for sending feedback to SAP is shown in the end. Default: true.

•SAPINST_STACK_XML:

Path and name of stack.xml file as described in SAP Note 1680045.

Como paso previo para poder conectar los sistemas on premise a SAP Datasphere o SAP Data Warehouse Cloud es instalar un DP agent. Este agente es un midellware que se encargará de traducir los comandos entre diferentes plataformas, traduciendo el formato del sistema origen al destino. Genera una carga mínima en el sistema donde se instala y lleva los adaptadores para las siguientes BBDD:

• DB2LogReaderAdapter
• MssqlLogReaderAdapter
• OracleLogReaderAdapter
• TeradataAdapter

Aunque también soporta las siguientes base de datos con el adaptador jdbc

más información : https://help.sap.com/docs/AGILE_DATA_PREPARATION/a8c7476dbef64e14b42939606e1d0c2e/cac0dc01fa704b16a98431101d648319.html?version=1.0.24&locale=en-US

https://support.sap.com/content/dam/launchpad/en_us/pam/pam-essentials/TIP/PAM_SAP_ADP_1_0.pdf