99.9% of the time the error ORA-65096: invalid common user or role name means you are logged into the CDB when you should be logged into a PDB. For example, if you used the default 19c installation settings, you should login to ORCLPDB (the PDB) instead of ORCL (the CDB). DANGER – If you insist … Read more
I have been struggling with this same issue for a couple of weeks and finally have a resolution. I had to disable the FIPS security policy, try setting this key: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy] “Enabled”=dword:00000000 to zero, it worked perfectly for me I was following your thread your blank password issue eventually pointed me here: https://community.oracle.com/thread/2557592?start=30&tstart=0
Oracle 12c version 12.1.0.2 (the latest version as of 11.11.2014) adds JSON support: https://docs.oracle.com/database/121/NEWFT/chapter12102.htm#BGBGADCC It’s been available since October 17th. https://blogs.oracle.com/db/entry/oracle_database_12c_release_1 If you are unable to patch/work with that version there is an excellent package written by Lewis Cunningham and Jonas Krogsboell: PL/JSON * http://pljson.sourceforge.net/ It’s an excellent package (I have used it in numerous … Read more
As an alternative to recursive SQL, you can also use the SQL MODEL clause. Personally, I find this a little easier to read than recursive SQL, though it is harder to write (because most people, like me, need to look up the syntax). — “test_data” is just a substitute for your real table, which I … Read more
99.9% of the time the error ORA-65096: invalid common user or role name means you are logged into the CDB when you should be logged into a PDB. For example, if you used the default 19c installation settings, you should login to ORCLPDB (the PDB) instead of ORCL (the CDB). DANGER – If you insist … Read more
If your 200+ packages work as intended with “old fashioned” syntax, let it be. SQL will not start to perform better after migration to ANSI syntax – it’s just different syntax. All that being said, ANSI syntax is cleaner – you are not going to normal join if you forget (+) in some multi-column outer … Read more
I deleted the ojdbc14.jar file and used ojdbc6.jar instead and it worked for me