Metadata file does not match checksum

[pven]

I have several errors when running vagrant up for ol7_122. I am not sure if I do something wrong, or it is 'the system against me'. It looks like it is having checksum-troubles with yum @ oracle.

error.txt

Is this fixable? :)

[oraclebase]

If I were to guess, I would suggest you don't have a network connection from your PC while running this build. I only ever see problems with mirrors when my network connection has problems.

[pven]

Thanks for the fast reply!

First it downloads the OS, so I think there is at least a connection at the beginning. When I go to the URL mentioned in the logging in my webbrowser it works. I can try later on with a disconnected VPN. Will get back to it later on today.

[oraclebase]

You only download the OS once. When you see it being loaded, it is being loaded from the copy on your PC. It is the OL7_122 RAC build you are trying right? I'll run the DNS and NODE2 of those now and see if I have any problems.

[oraclebase]

Looks like the DNS and NODE2 VMs build fine. These are using yum.oracle.com to get all the prerequisite packages, so it doesn't look like there is a fundamental issue with the vagrant build or vagrant box to me. I'm not going to run the NODE1 build, as it takes a long time :), and is using the same box and setup scripts for the prerequisites...

I see VirtualBox 6.1.16 has just been released. I'll be installing that and doing new builds of the oraclebase/oracle-8 and oraclebase/oracle-7 boxes today probably.

[pven]

I did a vagrant box update, I disabled all my VPN's (as in: close it), and now node 1 is up-and-running! :-)

Now trying node 2, first attempt looks like it is hanging. But I let it run for at least a few more hours.

[oraclebase]

Hi.

If this is a RAC build, the order is DNS, NODE2, NODE1. If this is a data gaurd build, the order is NODE1, NODE2.

Make sure you do the nodes in the order described in the README.md document.

Can you confirm which build you are actually trying to run please?

Cheers

Tim...

[pven]

Hi,

Sorry, forgot to mention: it is about dataguard (12.2). The first node succeeded, that was the first one I started. After this completed I started the second node, but that hangs:

...
    default:   Installing : 32:bind-utils-9.11.4-26.P2.el7.x86_64                      36/37
    default:
    default:   Installing : oracle-database-server-12cR2-preinstall-1.0-5.el7.x86_64   37/37

Thats it, it does not proceed. (I tried to use vagrant ssh to check what is going on, but ssh doesn;'t work yet.)

[oraclebase]

Hi.

I just did a clean build.

cd c:\git\oraclebase\vagrant\dataguard\ol7_122\node1 vagrant up

cd c:\git\oraclebase\vagrant\dataguard\ol7_122\node2 vagrant up

Both nodes built fine and I was left with a functioning Data Guard installation. Here's the output from the end of the node2 build.

    default: ******************************************************************************
    default: Validate configuration. Fri Oct 23 08:02:20 UTC 2020
    default: ******************************************************************************
    default: DGMGRL for Linux: Release 12.2.0.1.0 - Production on Fri Oct 23 08:03:20 2020
    default:
    default: Copyright (c) 1982, 2017, Oracle and/or its affiliates.  All rights reserved.
    default:
    default: Welcome to DGMGRL, type "help" for information.
    default: Connected to "cdb1"
    default: Connected as SYSDBA.
    default: DGMGRL>
    default:
    default:   Database Role:    Primary database
    default:
    default:   Ready for Switchover:  Yes
    default:
    default:   Managed by Clusterware:
    default:     cdb1:  NO
    default:     Warning: Ensure primary database's StaticConnectIdentifier property
    default:     is configured properly so that the primary database can be restarted
    default:     by DGMGRL after switchover
    default:
    default: DGMGRL>
    default:
    default:   Database Role:     Physical standby database
    default:   Primary Database:  cdb1
    default:
    default:   Ready for Switchover:  Yes
    default:   Ready for Failover:    Yes (Primary Running)
    default:
    default:   Flashback Database Status:
    default:     cdb1     :  On
    default:     cdb1_stby:  Off
    default:
    default:   Managed by Clusterware:
    default:     cdb1     :  NO
    default:     cdb1_stby:  NO
    default:     Warning: Ensure primary database's StaticConnectIdentifier property
    default:     is configured properly so that the primary database can be restarted
    default:     by DGMGRL after switchover
    default:
    default: DGMGRL>

I'm not sure why your stalls on the package updates. I would normally put that down to a network issue, but if you are not seeing that on your PC, that doesn't really make sense.

I assume there are no other issues (CPU, RAM, disk space) on your host PC?

Cheers

Tim...

[pven]

I rebooted the laptop, cleared everything using vagrant, re-installed, and now everything is working as expected. No idea what was wrong, but it is fixed.

Thans for your support!

[oraclebase]

Great news!