If you see something else other than the success message ** THE COPY HAS FINISHED SUCCESSFULLY** please open a SonarSource Support ticket and provide the complete DB Copy logs for investigation (logs are just the standard output of the tool).īase command and parameters java -jar sonar-db-copy-1.-jar-with-dependencies.Execute the base command with the correct parameters.This is to ensure that we don't have records being inserted/updated while copying. Stop the SonarQube instance connected to your source database.Unzip the DB Copy package provided by SonarSource Support on the machine where it will be executed.Make sure you execute this on a powerful machine that has fast network access to both database servers. You can now delete this temporary SonarQube instance.īecause this step is about copying data from source to target, the overall performance makes a difference.On Windows: terminate the StartSonar.bat script.On macOS: $SONAR_HOME/bin/macosx-universal-64/sonar.sh stop.On Linux: $SONAR_HOME/bin/linux-x86-64/sonar.sh stop.(Note: you also can export data from the custom SQL query results. Once this is done, it means that your target database had been populated with the SonarQube schema. In the Database Navigator select one or more tables you want to export. To do this, look at the logs/web.log file to see the line "Executed DB migrations: success". Verify that the SonarQube schema was correctly created.On Windows: %SONAR_HOME\bin\windows-x86-64\StartSonar.bat.On macOS: $SONAR_HOME/bin/macosx-universal-64/sonar.sh start.On Linux: $SONAR_HOME/bin/linux-x86-64/sonar.sh start.Start SonarQube using the script matching your operating system:.provide JDBC parameters in the $SONAR_HOME/conf/sonar.properties file). Configure SonarQube to connect to your target database (ie. ![]() ![]() Unzip SonarQube and put it in a relevant place on the machine.Download a SonarQube that matches the version and edition of your source instance.Re-created it in a new VPC (using terraform). I created a snapshot of the original db instance. Make sure you can connect to your target database. I have created a AWS RDS Postgresql db instance in one VPC and I need to 'move' it to another VPC.A workstation or any non-production server with Java available would be enough. As creating the database schema is a quick operation, you don't need to provision a specific server to do this.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |