Hello Db2 Genius Hub Support Team,

After the Database Management Console is deprecated I setup the new Db2 Genius Hub on a Red Hat Linux 9.7 System. On the same system I installed the Db2 Repository database.

==========================================
IBM Db2 Genius Hub - Product Status Check
==========================================

Component Status Summary:
---------------------------------------------------------------------------------
Component Status Details
---------------------------------------------------------------------------------
Liberty Server RUNNING PID: 720888 | Port(s): 11100(HTTP),11101(HTTPS)
Agentic AI Service RUNNING PID: 721801 | Port(s): 11108
Anomaly Detection Service RUNNING PID: 1015294 | Port(s): 11109
DRS Agent Service RUNNING PID: 721300 | Port(s): 11096
Job Scheduler Service RUNNING PID: 721382 | Port(s): 11107
Redis Service RUNNING PID: 721648 | Port(s): 6379
---------------------------------------------------------------------------------

Overall Status: [OK] All components are running

Trying the new Log Analysis following error occured:
Error
The RemoteOS service on the system dwqdb:50200 is down. Please enable it using https://ibm.com/docs/en/db2?topic=enable-remoteos-db2

For the setup I enabled the Remote OS service on the Db2 db2dwq instance on an AIX Server:
/db2/db2dwq/db2-remote-svc-1.0.0-aix/scripts> ./start.sh --jwt

========================================
db2remotesvc Start Script
========================================

[INFO] 2026-03-13 15:46:52 - Starting db2remotesvc service...
[INFO] 2026-03-13 15:46:52 - Using binary: /db2/db2dwq/db2-remote-svc-1.0.0-aix/db2remotesvc
[INFO] 2026-03-13 15:46:52 - Loading environment variables from .env file
[INFO] 2026-03-13 15:46:52 - Starting service with arguments: --enable-jwt=true
[INFO] 2026-03-13 15:46:52 - Starting in daemon mode...
[INFO] 2026-03-13 15:46:54 - Successfully started db2remotesvc (PID: 45154812)
[INFO] 2026-03-13 15:46:54 - Log file: /db2/db2dwq/db2-remote-svc-1.0.0-aix/logs/db2remotesvc.log
[INFO] 2026-03-13 15:46:54 - PID file: /db2/db2dwq/db2-remote-svc-1.0.0-aix/db2remotesvc.pid

========================================
[INFO] 2026-03-13 15:46:54 - Service started successfully
========================================

[INFO] 2026-03-13 15:46:54 - To check status: /db2/db2dwq/db2-remote-svc-1.0.0-aix/scripts/status.sh
[INFO] 2026-03-13 15:46:54 - To stop service: /db2/db2dwq/db2-remote-svc-1.0.0-aix/scripts/stop.sh
[INFO] 2026-03-13 15:46:54 - To view logs: tail -f /db2/db2dwq/db2-remote-svc-1.0.0-aix/logs/db2remotesvc.log

/db2/db2dwq/db2-remote-svc-1.0.0-aix/scripts> ./status.sh
db2remotesvc is RUNNING (PID: 45154812)

This is the changed .env file:
/db2/db2dwq/db2-remote-svc-1.0.0-aix> cat .env
# DB2 Agentic Utility Configuration

# Server configuration
SERVER_PORT=8080

# Metrics configuration
METRICS_CACHE_TTL=60

# DB2 configuration
# DB2 Profile Path Configuration (choose one of the following):
# Option 1: Set DB2_HOME and profile path will be automatically derived as DB2_HOME/db2profile
DB2_HOME=/db2/db2dwq/sqllib
# Option 2: Set DB2_PROFILE_PATH explicitly (overrides DB2_HOME if both are set)
# DB2_PROFILE_PATH=/home/db2inst1/sqllib/db2profile
# Option 3: Use pattern with %s for instance name (if neither DB2_HOME nor DB2_PROFILE_PATH is set)
# Default: /home/%s/sqllib/db2profile

# DB2 Timeout Configuration (in seconds)
# Timeout for individual DB2 commands (default: 120 seconds)
DB2_COMMAND_TIMEOUT=120
# Timeout for DB2 query operations (default: 120 seconds)
DB2_QUERY_TIMEOUT=120

# DB2 Connection Pool Configuration
# Maximum number of connections in the pool (default: 10)
DB2_POOL_MAX_SIZE=10
# Minimum number of connections to maintain (default: 2)
DB2_POOL_MIN_SIZE=2
# Maximum time a connection can be idle in minutes (default: 5)
DB2_POOL_MAX_IDLE_MINUTES=5
# Maximum lifetime of a connection in minutes (default: 30)
DB2_POOL_MAX_LIFETIME_MINUTES=30

# Security configuration
# API key is always required
# For production, generate a strong random key (min 16 chars)
# Example: API_KEY=$(openssl rand -base64 24)
#API_KEY=change_me_in_production
# Rate limit (requests per minute)
RATE_LIMIT=200
# TLS configuration
TLS_ENABLED=false
TLS_CERT=cert.pem
TLS_KEY=key.pem

# Application mode
# Set to "release" for production deployment
GIN_MODE=debug

# Development configuration
# Set to "true" to enable mock mode for development
MOCK_ENABLED=false

# Logging configuration
# Log level: DEBUG, INFO, WARN, ERROR, FATAL (default: INFO)
LOG_LEVEL=INFO
# Log file path (default: logs/db2remotesvc.log)
LOG_FILE_PATH=logs/db2remotesvc.log
# Maximum log file size in MB before rotation (default: 100)
LOG_MAX_SIZE_MB=100
# Maximum number of old log files to keep (default: 5)
LOG_MAX_BACKUPS=5

Why the message has the port 50200 - which is the the connection port (db2c_db2dwq 50200/tcp) (TCP/IP Service name (SVCENAME) = db2c_db2dwq) for the database and not the default 8080 port?

Best regards, Joachim

Hello Cintia,

Both ports are open:

(ip-address)8080 port [udp/webcache] succeeded!

(ip-address) 50200 port [udp/*] succeeded!

Best regards, Joachim

Hello Cintia,

Unfortunately no help from your colleagues (Case TS021657723):

Hi Joachim,

Thanks for reaching out. I have asked the support team to reopen the case TS021657723 and if you could upload the log files and the details for the issue. The team will review and update the case.

Regards,

Nidhi

I am asking control center team's help to route this case to console support team to continue the investigation. 

Hello Su Li Hou,

Thank you.

Best regards, Joachim

Hello Joachim,

Could you please let me know the port number provided in the Connections page under 'Enable Remote OS Service' ? 
After modifying the .env file, did you restart the remote OS Service in AIX?

Hello Thomas,

Best regards, Joachim