Tag Info

New answers tagged

1

These are the default values related to this: NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ os_authent_prefix string ops$ remote_os_authent boolean FALSE Set remote_os_authent to true: alter system set ...


0

When you login in the terminal, Oracle lets you in because the user oracle on the server 10.10.1.64 is a member of the OSDBA group on that machine. When you connect from SQL Developer on your laptop, it's a remote connection so OS Authentication isn't normally possible. You might be able to use SSH Authentication, see ...


3

You have an error in your query. The CTE m will return not a single row, but as many rows as in FCS_FP_TOMB. Then you are putting all of those rows into the row generator CTE n, whereas a row generator construct like you're using should get a single row. What I would do is to define m to return a single row with the minimum and maximum values, and then ...


0

After talking with some people with more Experience in Oracle than me, they told me I was right in my understanding. This query returns the references to an object (except the constraints) SELECT object_id, owner, object_name, object_type FROM sys.DBA_OBJECTS WHERE object_id IN (select object_id from ...


0

The problem is length or lengthb functions treat these special characters as 1 byte but write_text function (correctly) considers these as 2 bytes. Hence a mal-formed XML is sent to the server. To resolve this error please use the following instead of the length / lengthb function. lv_clob_length_bytes := ...


1

Check the source of both views: select dbms_metadata.get_ddl('VIEW', 'PUBLIC_DEPENDENCY', 'SYS') from dual; select dbms_metadata.get_ddl('VIEW', 'DBA_DEPENDENCIES', 'SYS') from dual; PUBLIC_DEPENDENCY queries directly from the dictionary table dependency$ and nothing else. DBA_DEPENDENCIES also queries dependency$, but joins some other tables and views as ...


2

Most probably this is fake alarm. the space UNDO tablespace is allocated differently then on other tablespaces. Oracle simply does not clean out old versions of block unless necessary. There are no real data in this tablespace. You UNDO space was really full you would get ORA-01555 Snapshot too old, or other types of errors. Check the view v$undostat.


1

Most probably this is fake alarm. the space UNDO tablespace is allocated differently then on other tablespaces. Oracle simply does not clean out old versions of block unless necessary. There are no real data in this tablespace. You UNDO space was really full you would get ORA-01555 Snapshot too old, or other types of errors. Check the view v$undostat. PS: ...



Top 50 recent answers are included