> Hi @oeMoe, can you please share how you call SQL*Plus? Is it just `sqlplus / as sysdba`? I think the issue is related with the `root` user which is the user to be logged into the container. However, the database is running under the `oracle` user and therefore `sqlplus / as sysdba` cannot attach to the process.
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 7k
- Forks
- 5.4k
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 9
Description
Hi @oeMoe, can you please share how you call SQL*Plus? Is it just
sqlplus / as sysdba? I think the issue is related with therootuser which is the user to be logged into the container. However, the database is running under theoracleuser and thereforesqlplus / as sysdbacannot attach to the process.
However, you should be able to log on using a connection string, e.g.:sqlplus sys/LetsDocker@//localhost:1521/XE as sysdba
I'm having same issue and i'm not getting this solution
what do you mean by connection string ?
Originally posted by @President-Temitope in https://github.com/oracle/docker-images/issues/332#issuecomment-864141289
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.
Research direction
The issue names no repository files, tests, or entry points. Read the linked discussion in issue #332, then reproduce the two SQL*Plus login forms in the Docker container; done requires a clearly documented working login path or a concrete repository change identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100