PDA

View Full Version : SLES12 migr. to SLES for SAP Appl° - Package not found!!!



Boubad
29-May-2017, 08:45
Where I can find such a package "SLES_SAP-Release"
regards
---------------------------------------- extract of the migration script execution --------------------------
Exchanging release packages...

+ cp -p SLES.prod-red28-05 SLES.prod
cp: cannot stat ‘SLES.prod-red28-05’: No such file or directory
+ zypper -n install -f SLES_SAP-release sles-release
Warning: The /etc/products.d/baseproduct symlink is dangling or missing!
The link must point to your core products .prod file in /etc/products.d.

Loading repository data...
Reading installed packages...
Forcing installation of 'sles-release-12.1-1.331.ppc64le' from repository 'SLES12-SP1-12.1-0'.
Package 'SLES_SAP-release' not found.

jmozdzen
30-May-2017, 14:03
Hi Boubad,

while I've not had to deal with these specific issues so far, it looks like you're missing the proper repositories (IOW, the "SLES for SAP Applications"-specific repositories).

Regards,
J

Boubad
04-Jun-2017, 09:36
Yes it's my doubt but I wander why it's not describe in the migration process.. and I don't now where to find such a repository!!!
any idea..... my search across the web was unsuccessful!!!!

thank's for your support!!

smflood
04-Jun-2017, 22:22
Boubad Wrote in message:

> Yes it's my doubt but I wander why it's not describe in the migration
> process.. and I don't now where to find such a repository!!!
> any idea..... my search across the web was unsuccessful!!!!

So you have SLES12 SP1 which you now want to migrate to SLES for
SAP Applications 12 SP1? Please can you post the output from "cat
/etc/*release".

Please can you also let us know which process you are following?
Is it as per TID 7017320[1]?

HTH.

[1] https://www.suse.com/support/kb/doc/?id=7017320
--
Simon Flood
SUSE Knowledge Partner


----Android NewsGroup Reader----
http://usenet.sinaapp.com/

Boubad
05-Jun-2017, 13:24
HI Simon

please find herein the cat /etc/os-release
# cat /etc/os-release
NAME="SLES"
VERSION="12-SP1"
VERSION_ID="12.1"
PRETTY_NAME="SUSE Linux Enterprise Server 12 SP1"
ID="sles"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:12:sp1"

NB: YES, the migration process I have applied is the "https://www.suse.com/support/kb/doc/?id=7018295" which is for HANA on Power PPC64LE.

ps: after running the migration script... running "zipper lr" shows that that OS name does not change anymore!!!

thanks for your support!!!!

Boubad
05-Jun-2017, 13:44
in addition, here is the trace log of the execution of the migration script:
# /usr/sbin/Migrate_SLES_to_SLES-for-SAP-12.sh
++ uname -m
+ ARCH=ppc64le
+ [[ 0 -ne 0 ]]
+ echo -e '\nThis script will migrate your installed\n
\tSUSE Linux Enterprise Server 12 SP1\n
to a\n
\tSUSE Linux Enterprise Server for SAP Applications 12 SP1.\n
Do you want to continue? [y/n]\n'

This script will migrate your installed

SUSE Linux Enterprise Server 12 SP1

to a

SUSE Linux Enterprise Server for SAP Applications 12 SP1.

Do you want to continue? [y/n]

+ start_migration
+ read ANSWER
y
+ case $ANSWER in
+ echo -e '\nNow starting the migration...\n'

Now starting the migration...

+ echo -e '\nThis script can use a local SMT server\n
instead of using SCC for the migration.\n
Do you want to use a local SMT server? [y/n]\n'

This script can use a local SMT server

instead of using SCC for the migration.

Do you want to use a local SMT server? [y/n]

+ use_smt
+ read ANSWER
y
+ case $ANSWER in
+ USE_SMT=y
+ echo -e '\nPlease enter the https URL to the SMT server
Example: https://mysmt.corp.com:\n'

Please enter the https URL to the SMT server
Example: https://mysmt.corp.com:

+ read SMT_URL
https://smtproxy.wdf.sap.corp
+ wget --no-verbose -q --no-check-certificate --dns-timeout 10 --connect-timeout 10 --output-document /tmp/smt.crt https://smtproxy.wdf.sap.corp/smt.crt
+ '[' 0 -ne 0 ']'
+ wget --no-verbose -q --no-check-certificate --dns-timeout 10 --connect-timeout 10 --output-document /tmp/clientSetup4SMT.sh https://smtproxy.wdf.sap.corp/repo/tools/clientSetup4SMT.sh
+ chmod +x /tmp/clientSetup4SMT.sh
++ openssl x509 -in /tmp/smt.crt -fingerprint
++ grep '^SHA1 Fingerprint='
++ cut -d= -f2
+ FINGERPRINT=0A:B6:2A:F4:7F:E5:59:84:7D:79:8A:1F:C4 :E1:7F:67:FD:7E:82:4C
+ '[' -x /usr/sbin/SUSEConnect ']'
+ '[' y = y ']'
+ /tmp/clientSetup4SMT.sh https://smtproxy.wdf.sap.corp/center/regsvc --fingerprint 0A:B6:2A:F4:7F:E5:59:84:7D:79:8A:1F:C4:E1:7F:67:FD :7E:82:4C --yes
+ /usr/sbin/SUSEConnect -p SLES_SAP/12.1-0/ppc64le --url https://smtproxy.wdf.sap.corp
+ rpm -e --nodeps sles-release
+ echo -e '\nExchanging release packages...\n'

Exchanging release packages...

+ zypper -n install -f SLES_SAP-release sles-release
+ rpm -e sles-release-DVD
+ cp /etc/default/grub /etc/default/grub-SLES12
+ sed s/SLES12/SLES_SAP-12/ -i /etc/default/grub
+ /sbin/update-bootloader --reinit
+ '[' -e /etc/zypp/repos.d/SLES12-12-0.repo ']'
+ '[' -e /etc/zypp/services.d/SUSE_Linux_Enterprise_Server_12_SP1_ppc64le.servic e ']'
+ for i in '/etc/zypp/repos.d/SUSE_Linux_Enterprise_Server_12_SP1_${ARCH}*'
+ '[' -e '/etc/zypp/repos.d/SUSE_Linux_Enterprise_Server_12_SP1_ppc64le*' ']'
+ rm -f /tmp/smt.crt /tmp/clientSetup4SMT.sh
+ echo -e '\nYou'\''re now subscribed to following channels:\n'

You're now subscribed to following channels:

+ zypper lr
Warning: The /etc/products.d/baseproduct symlink is dangling or missing!
The link must point to your core products .prod file in /etc/products.d.

# | Alias | Name | Enabled | GPG Check | Refresh
--+-------------------+-------------------+---------+-----------+--------
1 | SLES12-SP1-12.1-0 | SLES12-SP1-12.1-0 | Yes | (r ) Yes | No

smflood
05-Jun-2017, 14:25
On 05/06/17 13:34, Boubad wrote:

> please find herein the cat /etc/os-release
> # cat /etc/os-release
> NAME="SLES"
> VERSION="12-SP1"
> VERSION_ID="12.1"
> PRETTY_NAME="SUSE Linux Enterprise Server 12 SP1"
> ID="sles"
> ANSI_COLOR="0;32"
> CPE_NAME="cpe:/o:suse:sles:12:sp1"
>
> NB: YES, the migration process I have applied is the
> "https://www.suse.com/support/kb/doc/?id=7018295" which is for HANA on
> Power PPC64LE.

As you have noted, TID 7018295 is for migrating SLES to SLES for SAP
Applications on PowerPC hardware. Do you have PowerPC hardware? Please
can you post the output from "arch" or "uname -m".

If you don't have PowerPC you should use the procedure and script from
TID 7017320 as I previously linked - the packages are different as they
contain different versions of the Migrate_SLES_to_SLES-for-SAP-12.sh
script (although from a quick check I think running the PowerPC version
on 64-bit CPU shouldn't cause a problem).

> ps: after running the migration script... running "zipper lr" shows that
> that OS name does not change anymore!!!

Can you also let us know whether you're using a local SMT server instead
of the SUSE Customer Center (SCC) for access to products repositories
including updates?

HTH.
--
Simon
SUSE Knowledge Partner

------------------------------------------------------------------------
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------

Boubad
05-Jun-2017, 14:56
HI Simon,

here is th resquested command results:
# arch
ppc64le
# uname -m
ppc64le

yes I hane PowerPC64 machine running SUSE SLES12 SP1 OS.

in accordance with IBM collegues and and working into SAP VPN network, I use in a first stahe a SMT server until solving my issue... once the migration scrit working correctly, I run SUSEConnect to record my system!