You might be using Automatic Memory Management (AMM). AMM uses two initialization parameters: MEMORY_TARGET MEMORY_MAX_TARGET The shared memory file system should have enough space to accommodate the MEMORY_TARGET and MEMORY_MAX_TARGET values. To verify: In UNIX/Linux, you will have to set the shared memory file system accordingly. Verify: Set: For example,
have a look into this blog, the problem resolved for me by changing the column datatype from varchar(100) to varchar(100 char). in my case the data contains some umlaut characters. http://gerardnico.com/wiki/database/oracle/byte_or_character
RANK gives you the ranking within your ordered partition. Ties are assigned the same rank, with the next ranking(s) skipped. So, if you have 3 items at rank 2, the next rank listed would be ranked 5. DENSE_RANK again gives you the ranking within your ordered partition, but the ranks are consecutive. No ranks are … Read more
The keyword for Oracle PL/SQL is “ELSIF” ( no extra “E”), not ELSEIF (yes, confusing and stupid)
I’m mostly used to Apex 4.1, but this approach should work. You don’t need an LOV. Your report query should include both the MAST_ID and the TASK_NAME columns. Hide the TASK_NAME column and set MAST_ID as the linking column. If you set the Link Text (under Column Link) to #TASK_NAME#, you should get the desired result. Display As should be left at the default (Display as Text etc).
If that’s a SQLException thrown by Java, it’s most likely because you are trying to get or set a value from a ResultSet, but the index you are using isn’t within the range. For example, you might be trying to get the column at index 3 from the result set, but you only have two … Read more
For errors like this you should involve oracle support. Unfortunately you do not mention what oracle release you are using. The error can be related to optimizer bind peeking. Depending on the oracle version different workarounds apply. You have two ways to address this: upgrade to 11.2 set oracle parameter _optim_peek_user_binds = false Of course underscore parameters … Read more
I think you should not rely on the implicit conversion. It is a bad practice. Instead you should try like this: or like
No, prior to Oracle version 12.2, identifiers are not allowed to exceed 30 characters in length. See the Oracle SQL Language Reference. However, from version 12.2 they can be up to 128 bytes long. (Note: bytes, not characters).
If that’s a SQLException thrown by Java, it’s most likely because you are trying to get or set a value from a ResultSet, but the index you are using isn’t within the range. For example, you might be trying to get the column at index 3 from the result set, but you only have two … Read more