@alex_p_c_  @ranjith7  Can you try the following: Go to OSGI config: "Day CQ Link Checker Transformer"Add the following in the  “Blacklisted Paths”/libs/granite/core/contentThen, try logging in again via the login page 

I would say, compare the OSGI config file on both instances and make sure there is no syntax error. Also, make sure the package filter.xml has the filter param correctly set. If it is set to merge, it might not update the existing nodes. [1] https://jackrabbit.apache.org/filevault/filter.html 

Here is the command what worked for me:java -jar ./oak-upgrade-1.10.jar \ --copy-versions=false --copy-binaries \ --src-datastore=/CQ/63latest/crx-quickstart/repository/datastore \ --azureconfig=/CQ/63migrationtemp/crx-quickstart/install/org.apache.jackrabbit.oak.plugins.blob.datastore.A...

From what I can check internally, this has been replaced by A default site template[1] that is available out-of-the-box and that defines a theme for the Core Components and a set of corresponding templates that can be used to generate a new site from the Create Site Wizard. This default site templat...

I would recommend logging a support ticket in this case. The support team can reach out to Adobe Engineering for detailed explanation

Check the error.log file for errors. Also, Make sure the underlying Java version was not changed

The same version is only for that example shared above. It can be used to move from lower to higher version without issues

You can use the basic Auth to login via : http://<ip>:4503/libs/granite/core/content/login.html?sling:authRequestLogin=1 

Yes, oak-upgrade can be used for 6.2 to 6.5 migrations. See [1] for basic setup and commands: [1] https://medium.com/@bikkurthi/offline-content-migration-in-aem-using-oak-upgrade-b23baa395eb8 

You need to create a cfg.json OSGI config for repo init to create system users and assign permissions. See docs below:  [1] https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/aem-project-content-package-structure.html#repo-init