In this blog post we will cover how to manage the Veridata Server, Veridata Client and the Repository MySQL Database. This gives clarity to us, to understand which binaries to access in order to start/stop the services.
Veridata MySQL Repository
Verify the mysql repostiroy is running or not
[root@gghub bin]# ps -ef|grep mysqld
root 10258 2619 0 16:12 pts/0 00:00:00 sudo ../mysql-commercial-8.0.34-linux-glibc2.17-x86_64-minimal/bin/mysqld_safe --user=vdtrepouser --port=3306
root 10260 10258 0 16:12 pts/0 00:00:00 /bin/sh ../mysql-commercial-8.0.34-linux-glibc2.17-x86_64-minimal/bin/mysqld_safe --user=vdtrepouser --port=3306
vdtrepo+ 10359 10260 0 16:12 pts/0 00:00:02 /ogg/veridata/mysql-commercial-8.0.34-linux-glibc2.17-x86_64-minimal/bin/mysqld --basedir=/ogg/veridata/mysql-commercial-8.0.34-linux-glibc2.17-x86_64-minimal --datadir=/ogg/veridata/mysql-commercial-8.0.34-linux-glibc2.17-x86_64-minimal/data --plugin-dir=/ogg/veridata/mysql-commercial-8.0.34-linux-glibc2.17-x86_64-minimal/lib/plugin --user=vdtrepouser --log-error=gghub.err --pid-file=gghub.pid --port=3306
root 11037 9356 0 16:21 pts/0 00:00:00 grep --color=auto mysqld
[root@gghub bin]# The MySQL repository we should manage from the root user, now let’s stop the repository with root password.
[root@gghub bin]# cd /ogg/veridata/bin/
[root@gghub bin]# pwd
/ogg/veridata/bin
[root@gghub bin]# ls run.sh
run.sh
[root@gghub bin]# ./run.sh repoStop
INFO: Please enter mysql root user password, once its prompted
Enter password:
[root@gghub bin]# Verify the Repository Status after stopping
[root@gghub bin]# ./run.sh repoStatus
Enter MySQL user veridata password:
mysqladmin: [Warning] Using a password on the command line interface can be insecure. mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)' Check that mysqld is running and that the socket: '/tmp/mysql.sock' exists!
MySQL server is not running or encountered an error.
[root@gghub bin]# Now we will start the Repository Database,
root@gghub bin]# nohup /ogg/veridata/bin/run.sh repStart &
[1] 10217
[root@gghub bin]# nohup: ignoring input and appending output to 'nohup.out'
[root@gghub bin]# cat nohup.out
Unknown argument. Starting the server by default.
Java version:17.0.12
/ogg/veridata/bin/run.sh: line 63: read: read error: 0: Bad file descriptor
mysqladmin: [Warning] Using a password on the command line interface can be insecure. mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)' Check that mysqld is running and that the socket: '/tmp/mysql.sock' exists!
MySQL server is not running or encountered an error.
INFO: Please system root password once its prompted, then press CTRL C to continue...
Unknown argument. Starting the server by default.
Java version:17.0.12
...
..
.
Schema Migration started! /ogg/veridata/bin/../vdt-schema-migration-dummy.jar
Java HotSpot(TM) 64-Bit Server VM warning: Ignoring option --illegal-access=warn; support was removed in 17.0
WARNING: package com.sun.net.ssl.internal.ssl not in java.base
[root@gghub bin]# Verify if we able to connect the MySQL database using below command
[root@gghub bin]# /ogg/veridata/mysql-commercial-8.0.34-linux-glibc2.17-x86_64-minimal/bin/mysql -u veridata -p -h 127.0.0.1 -P 3306
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 13
Server version: 8.0.34-commercial MySQL Enterprise Server - Commercial
Copyright (c) 2000, 2023, Oracle and/or its affiliates.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql> show DATABASES;
+--------------------+
| Database |
+--------------------+
| VDUSER_VERIDATA |
| information_schema |
| performance_schema |
+--------------------+
3 rows in set (0.00 sec)
mysql> use VDUSER_VERIDATA;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
mysql>Veridata Server
Now we will access the Veridata server home. We have three options to use the binary.
- Stop – Stops the veridata server
- Start – Starts the veridata server in the background
- Run – Starts the veridata on screen with output
Reference: https://docs.oracle.com/en/middleware/goldengate/veridata/23/gvdug/administer1.html
Now we will stop the veridata server
[root@gghub bin]# ./run.sh stop
9194
[root@gghub bin]# Shutting down the server...
[root@gghub bin]# .Starting the server
[root@gghub bin]# ./run.sh start
Unknown argument. Starting the server by default.
Java version:17.0.12
Enter MySQL user veridata password:
mysqladmin: [Warning] Using a password on the command line interface can be insecure. mysqld is alive
MySQL server is up and running in the port: 3306
Schema Migration started! /ogg/veridata/bin/../vdt-schema-migration-dummy.jar
Java HotSpot(TM) 64-Bit Server VM warning: Ignoring option --illegal-access=warn; support was removed in 17.0
WARNING: package com.sun.net.ssl.internal.ssl not in java.base
2025-12-10T10:49:24+0000 INFO: startup: Launched java jar PID 10931
[root@gghub bin]#After that we can able to access the Veridata Server WEB UI
Veridata Agent
Export the JAVA Home and access to the binaries of the agent as below and then we will issue stopping the agent.
[oracle@ggate1 deployment]$ pwd
/ogg/veridata/deployment
[oracle@ggate1 deployment]$
[oracle@ggate1 deployment]$ export JAVA_HOME=/usr/java/jdk-17-oracle-x64
[oracle@ggate1 deployment]$ export PATH=$JAVA_HOME/bin:$PATH
[oracle@ggate1 deployment]$ ./agent.sh stop
[VERIAGT-BOOT] INFO Looking for home directory.
[VERIAGT-BOOT] INFO Found bootstrap class in file:/ogg/veridata/agent/JavaAgent.jar!/com/goldengate/veridata/agent/BootstrapNextGen.class.
[VERIAGT-BOOT] INFO Home directory: /ogg/veridata/agent
[VERIAGT-BOOT] INFO Preparing classpath.
[VERIAGT-BOOT] INFO Driver location: /ogg/veridata/agent/drivers
[VERIAGT-BOOT] INFO Drivers to load: ojdbc11-23.2.0.0.jar
[VERIAGT-BOOT] INFO Classpath:
[VERIAGT-BOOT] INFO /ogg/veridata/agent/JavaAgent.jar
[VERIAGT-BOOT] INFO /ogg/veridata/agent/drivers/ojdbc11-23.2.0.0.jar
[VERIAGT-BOOT] INFO /ogg/veridata/agent/agent-manifest.jar
[VERIAGT-BOOT] INFO Initializing.
[VERIAGT-BOOT] INFO Invoking startup method: public static void com.goldengate.veridata.agent.VeridataAgentNextGen.main(java.lang.String[])
2025-12-10 17:06:01.843 NOTIFICATION OGGV-60150 Configuring logging.
2025-12-10 17:06:01.925 NOTIFICATION OGGV-60151 Config file for logger is /ogg/veridata/deployment/config/odl.xml
2025-12-10 17:06:07.091 NOTIFICATION OGGV-60161 Shutdown request complete: OK
Validate if any processes are still running?
[oracle@ggate1 deployment]$ ps -ef|grep agent
oracle 2668 2613 0 12:49 ? 00:00:00 /usr/bin/ssh-agent /bin/sh -c exec -l /bin/bash -c "env GNOME_SHELL_SESSION_MODE=classic gnome-session --session gnome-classic"
oracle 9029 3372 0 17:06 pts/0 00:00:00 grep --color=auto agent
Now we will start the agent client
[oracle@ggate1 deployment]$ ./agent.sh start
[oracle@ggate1 deployment]$ ps -ef|grep agent
oracle 2668 2613 0 12:49 ? 00:00:00 /usr/bin/ssh-agent /bin/sh -c exec -l /bin/bash -c "env GNOME_SHELL_SESSION_MODE=classic gnome-session --session gnome-classic"
oracle 9053 2588 4 17:06 pts/0 00:00:00 /usr/java/jdk-17-oracle-x64/bin/java -Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration -Doracle.core.ojdl.logging.config.file=/ogg/veridata/deployment/config/odl.xml -Dhome=/ogg/veridata/agent -DagentHome=/ogg/veridata/deployment -XX:+UseParallelGC -Xmx1024M -Xms1024M -Dagent-manifest.jar=/ogg/veridata/agent/agent-manifest.jar -jar /ogg/veridata/agent/JavaAgent.jar
oracle 9081 3372 0 17:06 pts/0 00:00:00 grep --color=auto agent
[oracle@ggate1 deployment]$ We’ve covered all the components – Repository, Server and client how to manage them properly.
