Skip to main content

At first you get the warning:

 

2022-06-08 09:00:12|  1.4| 0.0|INFORM|Creating reader for format: Oracle Spatial Object

2022-06-08 09:00:12|  1.5| 0.0|INFORM|Performing query against ORACLE_SPATIAL dataset ` ----'

2022-06-08 09:00:12|  1.5| 0.0|INFORM|ORACLE Reader: Using Oracle Reader to read tables from database `', server type `ORACLE8i', server name `----', user name `----, password `***'

2022-06-08 09:00:12|  1.5| 0.0|INFORM|ORACLE Reader: Using Rich geometry.

2022-06-08 09:00:12|  1.5| 0.0|INFORM|Loaded module 'OCI' from file 'OCI.dll'

2022-06-08 09:00:12|  1.6| 0.1|INFORM|Environment variable ORACLE_HOME is not set.

2022-06-08 09:00:12|  1.6| 0.0|INFORM|Connecting to ORACLE database `----' with user name of `----' and password of `***'

2022-06-08 09:00:13|  1.6| 0.1|WARN |Error connecting to Oracle database: message was `ORA-01017: invalid username/password; logon denied'. (serverType=`ORACLE8i', serverName=`----', userName=`----', password=`***', dbname=`')

2022-06-08 09:00:13|  1.6| 0.0|INFORM|Failed to open database with username='----', retrying using uppercase username

2022-06-08 09:00:13|  1.6| 0.0|INFORM|Environment variable ORACLE_HOME is not set.

 

After the warning the connection is created.

 

2022-06-08 09:00:13|  1.6| 0.0|INFORM|Connecting to ORACLE database `----' with user name of `----' and password of `***'

2022-06-08 09:00:13|  1.6| 0.0|INFORM|Connected to ORACLE database `----'

2022-06-08 09:00:13|  1.6| 0.0|INFORM|Oracle database version is '12.2.0.1.0'

2022-06-08 09:00:13|  1.6| 0.0|INFORM|Environment variable ORACLE_HOME is not set.

2022-06-08 09:00:13|  1.6| 0.0|INFORM|Connecting to ORACLE database `----' with user name of ----' and password of `***'

2022-06-08 09:00:13|  1.6| 0.0|INFORM|Connected to ORACLE database `----'

 

It is not a big issue, but DBA reacts because they monitor this kind of warnings.

Is it possible to adjust the script so we don't get that warning anymore?

 

The FME version is 2020.2.But the issue is also present in older FME versions

 

With kind regards,

John van der Kleijn

Municipallity Eindhoven

the Netherlands

Usually you see that warning if you've put in your username in lowercase, FME automatically tries it in uppercase for you (presumably because lowercase usernames are not possible in Oracle) and if it's then correct the connection is then made successfully


Usually you see that warning if you've put in your username in lowercase, FME automatically tries it in uppercase for you (presumably because lowercase usernames are not possible in Oracle) and if it's then correct the connection is then made successfully

Thank's for the reply.

It solved the issue☝️


Reply