oracle / oracle/oracle-database-operator
SIDB instance is not created when running in k8s cluster with IPV6 addresses
@aditya059 is already working on this.
Since Nov 30, 2023.
- Dominant language
- Go
- Stars
- 192
- Forks
- 69
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 1
Description
The DB operator creates a SIDB pod but the the PDB is not available for connections.
`[speriyat@speriyat-1 speriyat]$ kubectl get singleinstancedatabase -n ns-visgtc my-oracle-sidb -o "jsonpath={.status.pdbConnectString}"
fc00:f853:ccd:e793::2:30361/ORCLPDB1
[speriyat@speriyat-1 speriyat]$ kubectl exec -it -n ns-visgtc pod/my-oracle-sidb-t9bwa bash
Defaulted container "my-oracle-sidb" out of: my-oracle-sidb, init-permissions (init), init-wallet (init)
[oracle@my-oracle-sidb-t9bwa ~]$ sqlplus
SQL*Plus: Release 19.0.0.0.0 - Production on Wed Nov 1 03:26:13 2023
Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle. All rights reserved.
Enter user-name: sys as sysdba
Enter password:
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0
SQL> connect sys/Oradoc_db1@[fc00:f853:ccd:e793::2]:30361/ORCLPDB1 as sysdba
ERROR:
ORA-12541: TNS:no listener
Warning: You are no longer connected to ORACLE.`
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.