- 3,722,882 Users
- 2,244,429 Discussions
- 7,850,127 Comments
Forum Stats
Discussions
Categories
- 16 Data
- 362.2K Big Data Appliance
- 7 Data Science
- 2K Databases
- 599 General Database Discussions
- 3.7K Java and JavaScript in the Database
- 32 Multilingual Engine
- 496 MySQL Community Space
- 7 NoSQL Database
- 7.7K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 421 SQLcl
- 59 SQL Developer Data Modeler
- 185K SQL & PL/SQL
- 21.1K SQL Developer
- 2.4K Development
- 3 Developer Projects
- 32 Programming Languages
- 135.6K Development Tools
- 12 DevOps
- 3K QA/Testing
- 327 Java
- 10 Java Learning Subscription
- 12 Database Connectivity
- 71 Java Community Process
- 2 Java 25
- 11 Java APIs
- 141.2K Java Development Tools
- 8 Java EE (Java Enterprise Edition)
- 153K Java Essentials
- 135 Java 8 Questions
- 86.2K Java Programming
- 270 Java Lambda MOOC
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 14 Java SE
- 13.8K Java Security
- 4 Java User Groups
- 22 JavaScript - Nashorn
- 18 Programs
- 147 LiveLabs
- 34 Workshops
- 9 Software
- 3 Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 4 Deutsche Oracle Community
- 16 Español
- 1.9K Japanese
- 3 Portuguese
What's the problem with my password while installing Apex 20.1?
User_UBZRD
Member Posts: 2
I am installing Apex 20.1 on my windows 10 with oracle 19c. After running the command : @apxchpwd.sql I get this error even after respecting all the password regulation and trying different combinations of mails and passwords : User "ADMIN" does not yet exist and will be created. Enter ADMIN's email [ADMIN] Enter ADMIN's password [] ERROR: ORA-01756: quoted string not properly terminated
Answers
-
That error message usually means that you've included a quote character, in this case the password?
-
No I haven't used any quotes in password or username or mail , and i respected all regulations.
-
An @ in the password is also a problem. This is used in the connect string un/[email protected]
-
Looks like you used a single quote as a special character, and it blew up the SQL in general the only special character that doesn't cause problem with any OS or client interface that I am aware of is the underscore ( _ ). jobs
