Re: [Spacewalk-list] Oracle 12/ 18 Database Support
Hey Richard, > On 20 May 2019, at 8:36 pm, Richard wrote: > > As we'd discussed on this thread that Oracle 18 should work, I modified the > /usr/share/perl5/vendor_perl/Spacewalk file and adjusted the > allowed_db_versions list to make it read: Yes, that’s one of the changes we’d make upstream once our testing has completed and our 2.9 build is published. We’re waiting for the general availability of Oracle Linux 8 before releasing our next version of Spacewalk, so some of this has been postponed until that’s completed. Cheers, Avi -- Avi Miller | Senior Manager | +61 (03) 8616-3496 Oracle Linux and VM Product Management 417 St Kilda Road, Melbourne VIC 3004 Australia ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
[Spacewalk-list] RHEL 8 AppStream repo on Spacewalk 2.9
Hi all, I have created a RHEL 8 distribution with the following parameters: Label: rhel-8.0-release-x86_64-dvd Tree Path: /path/to/rhel-server-8.0-x86_64 Installer Generation: Red Hat Enterprise Linux 8 Directly under /path/to/rhel-server-8.0-x86_64 I have the RHEL 8 DVD content: AppStream EULA images RPM-GPG-KEY-redhat-beta BaseOS extra_files.json isolinux RPM-GPG-KEY-redhat-release EFI GPL media.repo TRANS.TBL I created a RHEL 8 profile using a RHEL 8 base channel and selecting the following: Available Trees: rhel-8.0-release-x86_64-dvd The generated kickstart contains the following: url --url http://spacewalk/ks/dist/org/2/rhel-8.0-release-x86_64-dvd repo --name=AppStream --baseurl=http://spacewalk/ks/dist/org/2/rhel-8.0-release-x86_64-dvd A client using the generated kickstart file fails because the AppStream repository appears to be incorrect. If I manually modify the repo line in /var/lib/rhn/kickstarts/wizard/rhel-8_0-x86_64-dvd--2.cfg as follows then the installer will complete: repo --name=AppStream --baseurl=http://spacewalk/ks/dist/org/2/rhel-8.0-release-x86_64-dvd/AppStream I've not defined 'AppStream' in any configuration areas, so I presume Spacewalk is generating this automatically. Any idea why it might be generating an invalid URL? Many thanks, Richard. ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] Oracle 12/ 18 Database Support
On Thursday, May 2, 2019, 8:53:16 PM GMT+1, Avi Miller wrote: Hey Richard, > On 2 May 2019, at 7:01 pm, Richard wrote: > > My DBA tells me we are running in Oracle 11.2.0 compatibility mode (Database > Upgrade Guide). Is there any reason we should not move to Oracle 18.6.0 > compatibility ? None that I can think of. Our plan is to complete testing of Spacewalk 2.9 with the latest Oracle Instant Client 18c (which is available from yum.oracle.com with no click-through license any more[1]) and then push the spec file changes to shift to this client upstream. The updated Instant Client will work with all DB versions from 11gR2 all the way up to 19c. However, I don’t have an ETA on the completion of this testing yet. Our suite has to run across three database versions with the server on two major versions of the distro and two architectures for one of those versions, so it can take weeks to complete. :) Thanks, Avi [1] http://yum.oracle.com/repo/OracleLinux/OL7/oracle/instantclient/x86_64/index.html --- Hi Avi, By way of an update in case this is useful for you or anyone else. We were running Spacewalk 2.8 with Oracle 18.0.0. We upgraded to Spacewalk 2.9. The following error was generated when upgrading the database: # spacewalk-setup --external-oracle --upgrade* Setting up Oracle environment.* Setting up database.** Database: Setting up database connection for Oracle backend.Global Database Name or SID (requires tnsnames.ora)? X Username? X Password?Could not connect to the database. Your connection information may be incorrect. Error: Version [18.0.0] is not supported (does not match 12.2.0, 12.1.0, 11.2.0, 11.1.0, 10.2.0). As we'd discussed on this thread that Oracle 18 should work, I modified the /usr/share/perl5/vendor_perl/Spacewalk file and adjusted the allowed_db_versions list to make it read: my @allowed_db_versions = qw/18.0.0 12.2.0 12.1.0 11.2.0 11.1.0 10.2.0/; This allowed the installer to complete successfully and Spacewalk seems to be performing correctly. Richard. ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
