Feedback

Feedback

Did this article resolve your question/issue?

   

Article

"User does not exist" exist error when connecting to Oracle Service Cloud using an account with a period in the name with CfODBC Oracle Service Cloud driver

Printable View

Information

 
Title"User does not exist" exist error when connecting to Oracle Service Cloud using an account with a period in the name with CfODBC Oracle Service Cloud driver
URL NameUser-does-not-exist-exist-error-when-connecting-to-Oracle-Service-Cloud-using-an-account-with-a-period-in-the-name-with-CfODBC-Oracle-Service-Cloud-driver
Article Number000182386
EnvironmentProduct: Connect64 for ODBC Oracle Service Cloud driver
Version: 7.1
OS: Windows
Database: Oracle Service Cloud
Application: All supported applications
Question/Problem Description

When configuring the data source in ODBC Administrator and testing with my personal account (xxxx) the system will connect successfully.
When utilizing a service account (yyyy.xxxx) for automation to connect, an error occurs.

Steps to ReproduceAttempt to login using an account that contains a '.'
For e.g. username yyyy.xxxx
Observed Result:User yyyyxxxx does not exist
Expected Result: Connection should be successful
Clarifying Information
Error MessageUser does not exist
Defect Number
Enhancement Number
Cause

Create Database option in the Advanced Tab was set to 2 (Not Exists ) when connecting with the username yyyy.xxxx i.e. a user name with a period (.) in it 

User-added image


 
Resolution

Change the Create Database option to 1 (Force New ) for the connection to succeed.


 

 

Workaround
Notes

Details about the Create Database option :
If set to 0 - No, the driver uses the current embedded database specified by DatabaseName. If one does not exist, the connection fails.
If set to 1 - ForceNew, the driver deletes the current embedded database specified by Database and creates a new one at the same location.This causes all views, data caches, and map customizations defined in the current database to be lost.
If set to 2 - NotExist, the driver uses the current embedded database specified by DatabaseName. If one does not exist, the driver creates one. 
 

Last Modified Date1/24/2016 3:45 AM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.


Copyright © 2022 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.

Progress, Telerik, Ipswitch, Chef, Kemp, Flowmon and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.

Terms of Use Privacy Center Security Center Trademarks License Agreements Code of Conduct Careers Offices
Do Not Sell My Personal Information