Help Center/ GaussDB/ Service Overview/ Compatibility with Oracle/ Centralized Instances/ Advanced Packages
Updated on 2024-11-11 GMT+08:00
View PDF
Share

Advanced Packages

Table 1 lists the advanced packages compatible with GaussDB.

Table 1 Supported advanced packages

No.

Oracle Database

GaussDB

Difference

1

DBMS_LOB

DBE_LOB

For details about how to use it in GaussDB, see "Stored Procedure > Advanced Packages > Secondary Encapsulation Interfaces (Recommended) > DBE_LOB" in Developer Guide.

2

DBMS_RANDOM

DBE_RANDOM

For details about how to use it in GaussDB, see "Stored Procedure > Advanced Packages > Secondary Encapsulation Interfaces (Recommended) > DBE_RANDOM" in Developer Guide.

3

DBMS_OUTPUT

DBE_OUTPUT

For details about how to use it in GaussDB, see "Stored Procedure > Advanced Packages > Secondary Encapsulation Interfaces (Recommended) > DBE_OUTPUT" in Developer Guide.

4

UTL_RAW

DBE_RAW

For details about how to use it in GaussDB, see "Stored Procedure > Advanced Packages > Secondary Encapsulation Interfaces (Recommended) > DBE_RAW" in Developer Guide.

5

DBMS_SCHEDULER

DBE_SCHEDULER

For details about how to use it in GaussDB, see "Stored Procedure > Advanced Packages > Secondary Encapsulation Interfaces (Recommended) > DBE_SCHEDULER" in Developer Guide.

6

DBMS_UTILITY

DBE_UTILITY

For details about how to use it in GaussDB, see "Stored Procedure > Advanced Packages > Secondary Encapsulation Interfaces (Recommended) > DBE_UTILITY" in Developer Guide.

7

DBMS_SQL

DBE_SQL

For details about how to use it in GaussDB, see "Stored Procedure > Advanced Packages > Secondary Encapsulation Interfaces (Recommended) > DBE_SQL" in Developer Guide.

8

UTL_FILE

DBE_FILE

For details about how to use it in GaussDB, see "Stored Procedure > Advanced Packages > Secondary Encapsulation Interfaces (Recommended) > DBE_FILE" in Developer Guide.

9

DBMS_SESSION

DBE_SESSION

For details about how to use it in GaussDB, see "Stored Procedure > Advanced Packages > Secondary Encapsulation Interfaces (Recommended) > DBE_SESSION" in Developer Guide.

10

UTL_MATCH

DBE_MATCH

For details about how to use it in GaussDB, see "Stored Procedure > Advanced Packages > Secondary Encapsulation Interfaces (Recommended) > DBE_MATCH" in Developer Guide.

11

DBMS_APPLICATION_INFO

DBE_APPLICATION_INFO

For details about how to use it in GaussDB, see "Stored Procedure > Advanced Packages > Secondary Encapsulation Interfaces (Recommended) > DBE_APPLICATION_INFO" in Developer Guide.

12

DBMS_XMLDOM

DBE_XMLDOM

For details about information in GaussDB, see "Stored Procedure > Advanced Packages > Secondary Encapsulation Interfaces (Recommended) > DBE_XMLDOM" in Developer Guide.

13

DBMS_XMLPARSER

DBE_XMLPARSER

For details about information in GaussDB, see "Stored Procedure > Advanced Packages > Secondary Encapsulation Interfaces (Recommended) > DBE_XMLPARSER" in Developer Guide.

14

DBMS_ILM

DBE_ILM

For details about information in GaussDB, see "Stored Procedure > Advanced Packages > Secondary Encapsulation Interfaces (Recommended) > DBE_ILM" in Developer Guide.

15

DBMS_ILM_ADMIN

DBE_ILM_ADMIN

For details about information in GaussDB, see "Stored Procedure > Advanced Packages > Secondary Encapsulation Interfaces (Recommended) > DBE_ILM_ADMIN" in Developer Guide.

16

DBMS_COMPRESSION

DBE_COMPRESSION

For details about information in GaussDB, see "Stored Procedure > Advanced Packages > Secondary Encapsulation Interfaces (Recommended) > DBE_COMPRESSION" in Developer Guide.

17

DBMS_HEAT_MAP

DBE_HEAT_MAP

For details about information in GaussDB, see "Stored Procedure > Advanced Packages > Secondary Encapsulation Interfaces (Recommended) > DBE_HEAT_MAP" in Developer Guide.

18

DBMS_DESCRIBE

DBE_DESCRIBE

For details about information in GaussDB, see "Stored Procedure > Advanced Packages > Secondary Encapsulation Interfaces (Recommended) > DBE_DESCRIBE" in Developer Guide.

19

DBMS_XMLGEN

DBE_XMLGEN

For details about information in GaussDB, see "Stored Procedure > Advanced Packages > Secondary Encapsulation Interfaces (Recommended) > DBE_XMLGEN" in Developer Guide.

20

DBMS_STATS

DBE_STATS

For details about information in GaussDB, see "Stored Procedure > Advanced Packages > Secondary Encapsulation Interfaces (Recommended) > DBE_STATS" in Developer Guide.
Table 2 DBMS_LOB compatibility

No.

Oracle Database

GaussDB

Difference

1

APPEND Procedures

APPEND Procedures

-

2

CLOB2FILE Procedure

Not supported.

-

3

CLOSE Procedure

BFILECLOSE Procedure

GaussDB: The parameter type is BFILE, and no function overloading exists.

Oracle Database: There are three overloaded procedures. The procedures have three parameters lob_loc, lob_loc, and file_loc, which are of the BLOB, CLOB CHARACTER SET ANY_CS, and BFILE types, respectively.

4

COMPARE Functions

COMPARE Functions

GaussDB: There are three overloaded functions. The third parameter (len) is of the BIGINT type.

Oracle Database: There are three overloaded functions. The third parameter (amount) is of the INTEGER type.

5

CONVERTTOBLOB Procedure

LOB_CONVERTTOBLOB Procedure

GaussDB: This procedure has five parameters, and the third, fourth, and fifth parameters are of the BIGINT type.

Oracle Database: This procedure has eight parameters. In addition to all GaussDB parameters, the blob_csid, lang_context, and warning parameters are added, which are of the NUMBER, INTEGER, and INTEGER types, respectively. The third, fourth, and fifth parameters are of the INTEGER type.

6

CONVERTTOCLOB Procedure

LOB_CONVERTTOCLOB Procedure

GaussDB: This procedure has five parameters. The third, fourth, and fifth parameters are of the BIGINT type.

Oracle Database: This procedure has eight parameters. The third, fourth, and fifth parameters are of the INTEGER type. In addition to all GaussDB parameters, this procedure in Oracle Database adds three parameters: blob_csid, lang_context, and warning, which are of NUMBER, INTEGER, and INTEGER types, respectively.

7

COPY Procedures

LOB_COPY Functions

-

8

COPY_DBFS_LINK Procedures

Not supported.

-

9

COPY_FROM_DBFS_LINK

Not supported.

-

10

CREATETEMPORARY Procedures

CREATE_TEMPORARY Procedures

GaussDB: There are two overloaded procedures. The first parameter (lob_loc) of the first overloaded procedure is of the BLOB type, and the first parameter (lob_loc) of the second overloaded procedure is of the CLOB type. The third parameter (dur) of the two overloaded procedures is of the INTEGER type, and the default value is 10.

Oracle Database: There are two overloaded procedures. The first parameter (lob_loc) of the first overloaded procedure is of the BLOB type. The first parameter (lob_loc) of the second overloaded procedure is of the CLOB type. The third parameter (dur) of the two overloaded procedures is of the PLS_INTEGER type. The default value of dur of the first overloaded procedure is DBMS_LOB.SESSION, and the default value of dur of the second overloaded procedure is 10.

11

DBFS_LINK_GENERATE_PATH Functions

Not supported.

-

12

ERASE Procedures

LOB_ERASE Procedures

-

13

FILECLOSE Procedure

Not supported.

-

14

FILECLOSEALL Procedure

Not supported.

-

15

FILEEXISTS Function

Not supported.

-

16

FILEGETNAME Procedure

Not supported.

-

17

FILEISOPEN Function

Not supported.

-

18

FILEOPEN Procedure

Not supported.

-

19

FRAGMENT_DELETE Procedure

Not supported.

-

20

FRAGMENT_INSERT Procedures

Not supported.

-

21

FRAGMENT_MOVE Procedure

Not supported.

-

22

FRAGMENT_REPLACE Procedures

Not supported.

-

23

FREETEMPORARY Procedures

Not supported.

-

24

GET_DBFS_LINK Functions

Not supported.

-

25

GET_DBFS_LINK_STATE Procedures

Not supported.

-

26

GETCHUNKSIZE Functions

GETCHUNKSIZE Functions

-

27

GETCONTENTTYPE Functions

Not supported.

-

28

GETLENGTH Functions

Not supported.

-

29

GETOPTIONS Functions

Not supported.

-

30

GET_STORAGE_LIMIT Function

Not supported.

-

31

INSTR Functions

MATCH Functions

GaussDB: There are three overloaded functions. The third and fourth parameters of the three overloaded functions are of the BIGINT type.

Oracle Database: There are three overloaded functions. The third and fourth parameters of the three overloaded functions are of the INTEGER type.

32

ISOPEN Functions

Not supported.

-

33

ISREMOTE Function

Not supported.

-

34

ISSECUREFILE Function

Not supported.

-

35

ISTEMPORARY Functions

Not supported.

-

36

LOADBLOBFROMFILE Procedure

LOADBLOBFROMBFILE Procedure

-

37

LOADCLOBFROMFILE Procedure

LOADCLOBFROMBFILE Procedure

-

38

LOADFROMFILE Procedure

LOADFROMBFILE Procedure

-

39

MOVE_TO_DBFS_LINK Procedures

Not supported.

-

40

OPEN Procedures

BFILEOPEN Procedure

GaussDB: There is no overloaded procedure. The first parameter (bfile) is of the DBE_LOB.BFILE type, and the second parameter (open_mode) is of the TEXT type. Only the read mode is supported.

Oracle Database: There are three overloaded procedures. In the first overloaded procedure, the first parameter (lob_loc) is of the NOCOPY BLOB type, and the second parameter (openmode) is of the BINARY_INTEGER type. In the second overloaded procedure, the first parameter (lob_loc) is of the NOCOPY CLOB CHARACTER SET ANY_CS type, and the second parameter (openmode) is of the BINARY_INTEGER type. In the third overloaded procedure, the first parameter (file_loc) is of the NOCOPY BFILE type, and the second parameter (openmode) is of the BINARY_INTEGER type, and the value can only be file_readonly.

41

READ Procedures

READ Procedures

GaussDB: There are two overloaded procedures.

Oracle Database: There are three overloaded procedures. The first two overloaded procedures are the same as those in GaussDB. The third overloaded procedure includes four parameters: file_loc, amount, offset, and buffer, which are of the BFILE, NOCOPY INTEGER, INTEGER, and RAW types, respectively.

42

SET_DBFS_LINK Procedures

Not supported.

-

43

SETCONTENTTYPE Procedure

Not supported.

-

44

SETOPTIONS Procedures

Not supported.

-

45

SUBSTR Functions

LOB_SUBSTR Functions

-

46

TRIM Procedures

STRIP Functions

GaussDB: There are two overloaded procedures. The second parameter (newlen) of the two overloaded procedures is of the BIGINT type.

Oracle Database: There are two overloaded procedures. The second parameter (newlen) of the two overloaded procedures is of the INTEGER type.

47

WRITE Procedures

WRITE Functions

-

48

WRITEAPPEND Procedures

WRITEAPPEND Functions

-
Table 3 DBMS_RANDOM compatibility

No.

Oracle Database

GaussDB

Difference

1

INITIALIZE Procedure

Not supported.

-

2

NORMAL Function

Not supported.

-

3

RANDOM Function

Not supported.

-

4

SEED Procedures

DBE_RANDOM.SET_SEED Function

GaussDB: There is no overloaded function. The parameter is of the INTEGER type.

Oracle Database: There are two overloaded procedures. The parameter types of the two overloaded procedures are VARCHAR2 and BINARY_INTEGER, respectively.

5

STRING Function

Not supported.

-

6

TERMINATE Procedure

Not supported.

-

7

VALUE Functions

DBE_RANDOM.GET_VALUE Function

GaussDB: There is no overloaded function.

Oracle Database: The VALUE function without parameters is overloaded, and the return type is NUMBER.
Table 4 DBMS_OUTPUT compatibility

No.

Oracle Database

GaussDB

Difference

1

DISABLE Procedure

DISABLE Function

-

2

ENABLE Procedure

ENABLE Function

-

3

GET_LINE Procedure

GET_LINE Function

-

4

GET_LINES Procedure

GET_LINES Function

GaussDB: There is no overloaded function. The first parameter (lines) is of the VARCHAR[] type.

Oracle Database: There are two overloaded procedures. The first parameters (lines) of the two overloaded procedures are of the CHARARR and DBMSOUTPUT_LINESARRAY types, respectively.

5

NEW_LINE Procedure

NEW_LINE Function

-

6

PUT Procedure

PUT Function

GaussDB: If the character set of the database server (server_encoding) is not encoded in UTF-8 and the character encoding of the input parameter is valid UTF-8, this function converts character encoding based on the relationship "UTF8 > server_encoding" and then outputs the result regardless of the data type of the input parameter.

Oracle Database: If the character set of the database server (server_encoding) is not encoded in UTF-8, the character encoding of the input parameter is valid UTF-8, and the input parameter type is NVARCHAR2, this procedure coverts the character encoding based on the relationship "UTF8 > server_encoding" and then outputs the result. If the input parameter is of other character types, the character encoding is regarded as an invalid character and output as a placeholder.

7

PUT_LINE Procedure

PUT_LINE Function

GaussDB: If the character set of the database server (server_encoding) is not encoded in UTF-8 and the character encoding of the input parameter is valid UTF-8, this function converts character encoding based on the relationship "UTF8 > server_encoding" and then outputs the result regardless of the data type of the input parameter.

Oracle Database: If the character set of the database server (server_encoding) is not encoded in UTF-8, the character encoding of the input parameter is valid UTF-8, and the input parameter type is NVARCHAR2, this procedure coverts the character encoding based on the relationship "UTF8 > server_encoding" and then outputs the result. If the input parameter is of other character types, the character encoding is regarded as an invalid character and output as a placeholder.
Table 5 UTL_RAW compatibility

No.

Oracle Database

GaussDB

Difference

1

BIT_AND Function

BIT_AND Function

-

2

BIT_COMPLEMENT Function

BIT_COMPLEMENT Function

-

3

BIT_OR Function

BIT_OR Function

GaussDB: The two parameters are defined as the TEXT type and returned as the TEXT type.

Oracle Database: The two parameters are of the RAW type and returned as the RAW type.

4

BIT_XOR Function

BIT_XOR Function

-

5

CAST_FROM_BINARY_DOUBLE Function

CAST_FROM_BINARY_DOUBLE_TO_RAW Function

-

6

CAST_FROM_BINARY_FLOAT Function

CAST_FROM_BINARY_FLOAT_TO_RAW Function

GaussDB: The n parameter is of the FLOAT4 type.

Oracle Database: The n parameter is of the FLOAT type.

7

CAST_FROM_BINARY_INTEGER Function

CAST_FROM_BINARY_INTEGER_TO_RAW Function

GaussDB: The value parameter is of the BIGINT type.

Oracle Database: The value parameter is of the INTEGER type.

8

CAST_FROM_NUMBER Function

CAST_FROM_NUMBER_TO_RAW Function

GaussDB: The n parameter is of the NUMERIC type.

Oracle Database: The n parameter is of the NUMBER type.

9

CAST_TO_BINARY_DOUBLE Function

CAST_FROM_RAW_TO_BINARY_DOUBLE Function

-

10

CAST_TO_BINARY_FLOAT Function

CAST_FROM_RAW_TO_BINARY_FLOAT Function

GaussDB: The function returns the FLOAT4 type.

Oracle Database: The function returns the FLOAT type.

11

CAST_TO_BINARY_INTEGER Function

CAST_FROM_RAW_TO_BINARY_INTEGER Function

GaussDB: The endianess parameter is of the INTEGER type, and the function returns the INTEGER type.

Oracle Database: The endianess parameter is of the PLS_INTEGER type, and the function returns the BINARY_INTEGER type.

12

CAST_TO_NUMBER Function

CAST_FROM_RAW_TO_NUMBER Function

GaussDB: The function returns the NUMERIC type.

Oracle Database: The function returns the NUMBER type.

13

CAST_TO_NVARCHAR2 Function

CAST_FROM_RAW_TO_NVARCHAR2 Function

-

14

CAST_TO_RAW Function

CAST_FROM_VARCHAR2_TO_RAW Function

-

15

CAST_TO_VARCHAR2 Function

CAST_TO_VARCHAR2 Function

-

16

COMPARE Function

COMPARE Function

GaussDB: The function returns the INTEGER type.

Oracle Database: The function returns the NUMBER type.

17

CONCAT Function

CONCAT Function

-

18

CONVERT Function

CONVERT Function

-

19

COPIES Function

COPIES Function

GaussDB: The n parameter is of the NUMERIC type.

Oracle Database: The n parameter is of the NUMBER type.

20

LENGTH Function

GET_LENGTH Function

GaussDB: The function returns the INTEGER type.

Oracle Database: The function returns the NUMBER type.

21

OVERLAY Function

OVERLAY Function

-

22

REVERSE Function

REVERSE Function

-

23

SUBSTR Function

SUBSTR Function

GaussDB: The lob_loc parameter is of the BLOB type. The off_set parameter is of the INTEGER type and its default value is 1. The amount parameter is of the INTEGER type and its default value is 32767.

Oracle Database: The r parameter is of the RAW type. The pos parameter is of the BINARY_INTEGER type and has no default value. The len parameter is of the BINARY_INTEGER type and its default value is NULL.

24

TRANSLATE Function

TRANSLATE Function

-

25

TRANSLITERATE Function

TRANSLITERATE Function

-

26

XRANGE Function

XRANGE Function

GaussDB: The start_byte and end_byte parameters do not have default values.

Oracle Database: The default values of the start_byte and end_byte parameters are NULL.
Table 6 DBMS_SCHEDULER compatibility

No.

Oracle Database

GaussDB

1

ADD_EVENT_QUEUE_SUBSCRIBER Procedure

Not supported.

2

ADD_GROUP_MEMBER Procedure

Not supported.

3

ADD_JOB_EMAIL_NOTIFICATION Procedure

Not supported.

4

ADD_TO_INCOMPATIBILITY Procedure

Not supported.

5

ALTER_CHAIN Procedure

Not supported.

6

ALTER_RUNNING_CHAIN Procedure

Not supported.

7

CLOSE_WINDOW Procedure

Not supported.

8

COPY_JOB Procedure

Not supported.

9

CREATE_CHAIN Procedure

Not supported.

10

CREATE_CREDENTIAL Procedure

CREATE_CREDENTIAL Procedure

11

CREATE_DATABASE_DESTINATION Procedure

Not supported.

12

CREATE_EVENT_SCHEDULE Procedure

Not supported.

13

CREATE_FILE_WATCHER Procedure

Not supported.

14

CREATE_GROUP Procedure

Not supported.

15

CREATE_INCOMPATIBILITY Procedure

Not supported.

16

CREATE_JOB Procedure

CREATE_JOB Procedure

17

CREATE_JOB_CLASS Procedure

CREATE_JOB_CLASS Procedure

18

CREATE_JOBS Procedure

Not supported.

19

CREATE_PROGRAM Procedure

CREATE_PROGRAM Procedure

20

CREATE_RESOURCE Procedure

Not supported.

21

CREATE_SCHEDULE Procedure

CREATE_SCHEDULE Procedure

22

CREATE_WINDOW Procedure

Not supported.

23

DEFINE_ANYDATA_ARGUMENT Procedure

Not supported.

24

DEFINE_CHAIN_EVENT_STEP Procedure

Not supported.

25

DEFINE_CHAIN_RULE Procedure

Not supported.

26

DEFINE_CHAIN_STEP Procedure

Not supported.

27

DEFINE_METADATA_ARGUMENT Procedure

Not supported.

28

DEFINE_PROGRAM_ARGUMENT Procedure

DEFINE_PROGRAM_ARGUMENT Procedure

29

DISABLE Procedure

DISABLE Procedure

30

DROP_AGENT_DESTINATION Procedure

Not supported.

31

DROP_CHAIN Procedure

Not supported.

32

DROP_CHAIN_RULE Procedure

Not supported.

33

DROP_CHAIN_STEP Procedure

Not supported.

34

DROP_CREDENTIAL Procedure

DROP_CREDENTIAL Procedure

35

DROP_DATABASE_DESTINATION Procedure

Not supported.

36

DROP_FILE_WATCHER Procedure

Not supported.

37

DROP_GROUP Procedure

Not supported.

38

DROP_INCOMPATIBILITY Procedure

Not supported.

39

DROP_JOB Procedure

DROP_JOB Procedure

40

DROP_JOB_CLASS Procedure

DROP_JOB_CLASS Procedure

41

DROP_PROGRAM Procedure

DROP_PROGRAM Procedure

42

DROP_PROGRAM_ARGUMENT Procedure

Not supported.

43

DROP_SCHEDULE Procedure

DROP_SCHEDULE Procedure

44

DROP_WINDOW Procedure

Not supported.

45

ENABLE Procedure

ENABLE Procedure

46

END_DETACHED_JOB_RUN Procedure

Not supported.

47

EVALUATE_CALENDAR_STRING Procedure

EVALUATE_CALENDAR_STRING Procedure

48

EVALUATE_RUNNING_CHAIN Procedure

Not supported.

49

GENERATE_JOB_NAME Function

GENERATE_JOB_NAME Function

50

GET_AGENT_INFO Function

Not supported.

51

GET_AGENT_VERSION Function

Not supported.

52

GET_ATTRIBUTE Procedure

Not supported.

53

GET_FILE Procedure

Not supported.

54

GET_SCHEDULER_ATTRIBUTE Procedure

Not supported.

55

OPEN_WINDOW Procedure

Not supported.

56

PURGE_LOG Procedure

Not supported.

57

PUT_FILE Procedure

Not supported.

58

REMOVE_EVENT_QUEUE_SUBSCRIBER Procedure

Not supported.

59

REMOVE_FROM_INCOMPATIBILITY Procedure

Not supported.

60

REMOVE_GROUP_MEMBER Procedure

Not supported.

61

REMOVE_JOB_EMAIL_NOTIFICATION Procedure

Not supported.

62

RESET_JOB_ARGUMENT_VALUE Procedure

Not supported.

63

RUN_CHAIN Procedure

Not supported.

64

RUN_JOB Procedure

RUN_JOB Procedure

65

SET_AGENT_REGISTRATION_PASS Procedure

Not supported.

66

SET_ATTRIBUTE Procedure

SET_ATTRIBUTE Procedure

67

SET_ATTRIBUTE_NULL Procedure

Not supported.

68

SET_JOB_ANYDATA_VALUE Procedure

Not supported.

69

SET_JOB_ARGUMENT_VALUE Procedure

SET_JOB_ARGUMENT_VALUE Procedure

70

SET_JOB_ATTRIBUTES Procedure

Not supported.

71

SET_RESOURCE_CONSTRAINT Procedure

Not supported.

72

SET_SCHEDULER_ATTRIBUTE Procedure

Not supported.

73

STOP_JOB Procedure

STOP_JOB Procedure
Table 7 DBMS_UTILITY compatibility

No.

Oracle Database

GaussDB

Difference

1

ACTIVE_INSTANCES Procedure

Not supported.

-

2

ANALYZE_DATABASE Procedure

Not supported.

-

3

ANALYZE_PART_OBJECT Procedure

Not supported.

-

4

ANALYZE_SCHEMA Procedure

Not supported.

-

5

CANONICALIZE Procedure

CANONICALIZE Procedure

GaussDB: The default size of the canon_len parameter is 1024 bytes.

Oracle Database: The canon_len parameter has no default value.

6

COMMA_TO_TABLE Procedures

COMMA_TO_TABLE Procedure

GaussDB: The tab parameter is a VARCHAR2 array.

Oracle Database: There are two overloaded procedures. The tab parameter can be of the uncl_array or lname_array type.

7

COMPILE_SCHEMA Procedure

Not supported.

-

8

CREATE_ALTER_TYPE_ERROR_TABLE Procedure

Not supported.

-

9

CURRENT_INSTANCE Function

Not supported.

-

10

DATA_BLOCK_ADDRESS_BLOCK Function

Not supported.

-

11

DATA_BLOCK_ADDRESS_FILE Function

Not supported.

-

12

DB_VERSION Procedure

DB_VERSION Procedure

GaussDB: There is only the version parameter, which is of the VARCHAR2 type. Oracle Database: There are the version and compatibility parameters, which are of the VARCHAR2 type.

13

EXEC_DDL_STATEMENT Procedure

EXEC_DDL_STATEMENT Function

GaussDB: The parse_string parameter is of the TEXT type.

Oracle Database: The parse_string parameter is of the VARCHAR2 type.

14

EXPAND_SQL_TEXT Procedure

EXPAND_SQL_TEXT Function

GaussDB: The output_sql_text parameter is of the CLOB type.

Oracle Database: The output_sql_text parameter is of the NOCOPY CLOB type. The OUT parameter is transferred by reference.

15

FORMAT_CALL_STACK Function

FORMAT_CALL_STACK Function

GaussDB: The function returns the TEXT type.

Oracle Database: The function returns the VARCHAR2 type.

16

FORMAT_ERROR_BACKTRACE Function

FORMAT_ERROR_BACKTRACE Function

GaussDB: The function returns the TEXT type.

Oracle Database: The function returns the VARCHAR2 type.

17

FORMAT_ERROR_STACK Function

FORMAT_ERROR_STACK Function

GaussDB: The function returns the TEXT type.

Oracle Database: The function returns the VARCHAR2 type.

18

GET_CPU_TIME Function

GET_CPU_TIME Function

GaussDB: The function returns the BIGINT type.

Oracle Database: The function returns the NUMBER type.

19

GET_DEPENDENCY Procedure

Not supported.

-

20

GET_ENDIANNESS Function

GET_ENDIANNESS Function

GaussDB: The function returns the INTEGER type.

Oracle Database: The function returns the NUMBER type.

21

GET_HASH_VALUE Function

GET_HASH_VALUE Function

GaussDB: The base and hash_size parameters and the return types are all INTEGER.

Oracle Database: The base and hash_size parameters and the return types are all NUMBER.

22

GET_PARAMETER_VALUE Function

Not supported.

-

23

GET_SQL_HASH Function

GET_SQL_HASH Function

GaussDB: The last4bytes parameter of the BIGINT type specifies the last four bytes of an MD5 hash value and is displayed as an unsigned integer. The function returns the BIGINT type.

Oracle Database: The pre10ihash parameter of the NUMBER type is used to store the 4-byte hash value among the 16 bytes calculated by MD5.

24

GET_TIME Function

GET_TIME Function

GaussDB: The function returns the BIGINT type.

Oracle Database: The function returns the NUMBER type.

25

GET_TZ_TRANSITIONS Procedure

Not supported.

-

26

INVALIDATE Procedure

Not supported.

-

27

IS_BIT_SET Function

IS_BIT_SET Function

GaussDB: The n parameter and return value type are both INTEGER.

Oracle Database: The n parameter and return value type are both NUMBER.

28

IS_CLUSTER_DATABASE Function

IS_CLUSTER_DATABASE Function

-

29

MAKE_DATA_BLOCK_ADDRESS Function

Not supported.

-

30

NAME_RESOLVE Procedure

NAME_RESOLVE Procedure

GaussDB: The context and part1_type parameters are of the INTEGER type, and the object_number parameter is of the OID type. GaussDB does not support implicit conversion from NUMBER to OID.

Oracle Database: The context, part1_type, and object_number parameters are of the NUMBER type.

31

NAME_TOKENIZE Procedure

NAME_TOKENIZE Procedure

GaussDB: The nextpos parameter is of the INTEGER type.

Oracle Database: The nextpos parameter is of the BINARY_INTEGER type.

32

OLD_CURRENT_SCHEMA Function

OLD_CURRENT_SCHEMA Function

GaussDB: The function returns the VARCHAR type.

Oracle Database: The function returns the VARCHAR2 type.

33

OLD_CURRENT_USER Function

OLD_CURRENT_USER Function

GaussDB: The function returns the TEXT type.

Oracle Database: The function returns the VARCHAR2 type.

34

PORT_STRING Function

Not supported.

-

35

SQLID_TO_SQLHASH Function

Not supported.

-

36

TABLE_TO_COMMA Procedures

TABLE_TO_COMMA Procedure

GaussDB: The tab parameter is a VARCHAR2 array.

Oracle Database: There are two overloaded stored procedures. The tab parameter can be of the uncl_array or lname_array type.

37

VALIDATE Procedure

Not supported.

-

38

WAIT_ON_PENDING_DML Function

Not supported.

-
Table 8 DBMS_SQL compatibility

No.

Oracle Database

GaussDB

Difference

1

BIND_ARRAY Procedures

SQL_BIND_ARRAY Function

-

2

BIND_VARIABLE Procedures

SQL_BIND_VARIABLEFunction

-

3

BIND_VARIABLE_PKG Procedure

Not supported.

-

4

CLOSE_CURSOR Procedure

SQL_UNREGISTER_CONTEXT Function

-

5

COLUMN_VALUE Procedure

GET_RESULT Procedure

-

6

COLUMN_VALUE_LONG Procedure

Not supported.

-

7

DEFINE_ARRAY Procedure

SET_RESULTS_TYPE Procedure

-

8

DEFINE_COLUMN Procedures

SET_RESULT_TYPE Procedure

-

9

DEFINE_COLUMN_CHAR Procedure

Not supported.

-

10

DEFINE_COLUMN_LONG Procedure

Not supported.

-

11

DEFINE_COLUMN_RAW Procedure

Not supported.

-

12

DEFINE_COLUMN_ROWID Procedure

Not supported.

-

13

DESCRIBE_COLUMNS Procedure

DESCRIBE_COLUMNS Procedure

-

14

DESCRIBE_COLUMNS2 Procedure

Not supported.

-

15

DESCRIBE_COLUMNS3 Procedure

Not supported.

-

16

EXECUTE Function

SQL_RUN Function

-

17

EXECUTE_AND_FETCH Function

RUN_AND_NEXT Function

-

18

FETCH_ROWS Function

NEXT_ROW Function

-

19

GET_NEXT_RESULT Procedures

Not supported.

-

20

IS_OPEN Function

IS_ACTIVE Function

-

21

LAST_ERROR_POSITION Function

Not supported.

-

22

LAST_ROW_COUNT Function

LAST_ROW_COUNT Function

-

23

LAST_ROW_ID Function

Not supported.

-

24

LAST_SQL_FUNCTION_CODE Function

Not supported.

-

25

OPEN_CURSOR Functions

REGISTER_CONTEXT Function

-

26

PARSE Procedures

Supported, with differences.

In GaussDB, the SQL_SET_SQL function does not support overloading.

27

RETURN_RESULT Procedures

Not supported.

-

28

TO_CURSOR_NUMBER Function

Not supported.

-

29

TO_REFCURSOR Function

Not supported.

-

30

VARIABLE_VALUE Procedures

GET_VARIABLE_RESULT Procedures

-

31

VARIABLE_VALUE_PKG Procedure

Not supported.

-
Table 9 DBMS_SQL data type compatibility

No.

Oracle Database

GaussDB

1

DBMS_SQL DESC_REC

DBE_SQL.DESC_REC

2

DBMS_SQL DATE_TABLE

DBE_SQL.DATE_TABLE

3

DBMS_SQL NUMBER_TABLE

DBE_SQL.NUMBER_TABLE

4

DBMS_SQL VARCHAR2_TABLE

DBE_SQL.VARCHAR2_TABLE

5

DBMS_SQL BLOB_TABLE

DBE_SQL.BLOB_TABLE
Table 10 UTL_FILE compatibility

No.

Oracle Database

GaussDB

Difference

1

FCLOSE Procedure

CLOSE Procedure

-

2

FCLOSE_ALL Procedure

CLOSE_ALL Procedure

-

3

FCOPY Procedure

COPY Procedure

-

4

FFLUSH Procedure

FLUSH Procedure

-

5

FGETATTR Procedure

GET_ATTR Procedure

-

6

FGETPOS Function

GET_POS Function

-

7

FOPEN Function

FOPEN Function

-

8

FOPEN_NCHAR Function

FOPEN_NCHAR Function

-

9

FREMOVE Procedure

REMOVE Procedure

-

10

FRENAME Procedure

RENAME Procedure

-

11

FSEEK Procedure

SEEK Procedure

-

12

GET_LINE Procedure

READ_LINE Procedure

-

13

GET_LINE_NCHAR Procedure

READ_LINE_NCHAR Procedure

-

14

GET_RAW Procedure

GET_RAW Procedure

-

15

IS_OPEN Function

IS_OPEN Function

-

16

NEW_LINE Procedure

Supported, with differences in the NEW_LINE function

GaussDB defines the API as a function.

17

PUT Procedure

Supported, with differences in the WRITE function

GaussDB defines the API as a function.

18

PUT_LINE Procedure

Supported, with differences in the WRITE_LINE function

GaussDB defines the API as a function.

19

PUT_LINE_NCHAR Procedure

Supported, with differences in the WRITE_LINE_NCHAR function

GaussDB defines the API as a function.

20

PUT_NCHAR Procedure

Supported, with differences in the WRITE_NCHAR function

GaussDB defines the API as a function.

21

PUTF Procedure

Supported, with differences in the FORMAT_WRITE function

GaussDB defines the API as a function.

22

PUTF_NCHAR Procedure

Supported, with differences in the FORMAT_WRITE_NCHAR function

GaussDB defines the API as a function.

23

PUT_RAW Procedure

Supported, with differences in the PUT_RAW function

GaussDB defines the API as a function.
Table 11 DBMS_SESSION compatibility

No.

Oracle Database

GaussDB

Difference

1

CLEAR_ALL_CONTEXT Procedure

Not supported.

-

2

CLEAR_CONTEXT Procedure

CLEAR_CONTEXT Function

-

3

CLEAR_IDENTIFIER Procedure

Not supported.

-

4

CLOSE_DATABASE_LINK Procedure

Not supported.

-

5

CURRENT_IS_ROLE_ENABLED Function

Not supported.

-

6

FREE_UNUSED_USER_MEMORY Procedure

Not supported.

-

7

GET_PACKAGE_MEMORY_UTILIZATION Procedure

Not supported.

-

8

IS_ROLE_ENABLED Function

Not supported.

-

9

IS_SESSION_ALIVE Function

Not supported.

-

10

LIST_CONTEXT Procedures

Not supported.

-

11

MODIFY_PACKAGE_STATE Procedure

MODIFY_PACKAGE_STATE Procedure

GaussDB: The scenario where flags is set to 1 is supported.

Oracle Database: The scenario where flags is set to 1 or 2 is supported.

12

RESET_PACKAGE Procedure

Not supported.

-

13

SESSION_IS_ROLE_ENABLED Function

Not supported.

-

14

SESSION_TRACE_DISABLE Procedure

Not supported.

-

15

SESSION_TRACE_ENABLE Procedure

Not supported.

-

16

SET_CONTEXT Procedure

SET_CONTEXT Function

GaussDB: There are the namespace, attribute, and value parameters of the TEXT type.

Oracle Database: There are the namespace, attribute, value, username, and client_id parameters of the VARCHAR2 type.

17

SET_EDITION_DEFERRED Procedure

Not supported.

-

18

SET_IDENTIFIER Procedure

Not supported.

-

19

SET_NLS Procedure

Not supported.

-

20

SET_ROLE Procedure

Not supported.

-

21

SET_SQL_TRACE Procedure

Not supported.

-

22

SLEEP Procedure

Not supported.

-

23

SWITCH_CURRENT_CONSUMER_GROUP Procedure

Not supported.

--

24

UNIQUE_SESSION_ID Function

Not supported.

-
Table 12 UTL_MATCH compatibility

No.

Oracle Database

GaussDB

Difference

1

EDIT_DISTANCE Function

Not supported.

-

2

EDIT_DISTANCE_SIMILARITY Function

EDIT_DISTANCE_SIMILARITY Function

GaussDB: The str1 and str2 parameters are of the TEXT type, and the function returns the INTEGER type.

Oracle Database: The s1 and s2 parameters are of the VARCHAR2 type, and the function returns the PLS_INTEGER type.

3

JARO_WINKLER Function

Not supported.

-

4

JARO_WINKLER_SIMILARITY Function

Not supported.

-
Table 13 DBMS_APPLICATION_INFO compatibility

No.

Oracle Database

GaussDB

Difference

1

READ_CLIENT_INFO Procedure

READ_CLIENT_INFO Function

GaussDB: The client_info parameter is of the TEXT type.

Oracle Database: The client_info parameter is of the VARCHAR2 type.

2

READ_MODULE Procedure

READ_MODULE Procedure

GaussDB: The module_name and action_name parameters are of the TEXT type.

Oracle Database: The module_name and action_name parameters are of the VARCHAR2 type.

3

SET_ACTION Procedure

SET_ACTION Procedure

GaussDB: The action_name parameter is of the TEXT type.

Oracle Database: The action_name parameter is of the VARCHAR2 type.

4

SET_CLIENT_INFO Procedure

SET_CLIENT_INFO Function

GaussDB: The str parameter is of the TEXT type, and the return type is VOID.

Oracle Database: The client_info parameter is of the VARCHAR2 type and no value is returned. Both of them are written to the client. The maximum length is 64 bytes. If the length exceeds 64 bytes, it will be truncated.

5

SET_MODULE Procedure

SET_MODULE Procedure

GaussDB: The module_name and action_name parameters are of the TEXT type.

Oracle Database: The module_name and action_name parameters are of the VARCHAR2 type.

6

SET_SESSION_LONGOPS Procedure

Not supported.

-
Table 14 DBMS_XMLDOM compatibility

No.

Oracle Database

GaussDB

Difference

1

DBMS_XMLDOM.APPENDCHILD

DBE_XMLDOM.APPENDCHILD
  • GaussDB: The error message "operation not support" is displayed for the APPEND ATTR node under the DOCUMENT node.

    Oracle Database: No error is reported in this scenario, but the mounting fails.

  • GaussDB: The error message "operation not support" is displayed for the APPEND ATTR node under the ATTR node.

    Oracle Database: No error is reported in this scenario, but the mounting fails.

  • GaussDB: When multiple child nodes of the ATTR type are added to a parent node, the child nodes with the same key value cannot exist under the same parent node.

    Oracle Database: Child nodes with the same key value can exist under the same parent node.

2

DBMS_XMLDOM.CREATEELEMENT

DBE_XMLDOM.CREATEELEMENT

-

3

DBMS_XMLDOM.CREATETEXTNODE

DBE_XMLDOM.CREATETEXTNODE

-

4

DBMS_XMLDOM.FREEDOCUMENT

DBE_XMLDOM.FREEDOCUMENT

GaussDB: Objects are not released immediately. They are released after a certain number of objects are accumulated. All nodes in the document are invalid.

Oracle Database: The object is released immediately.

5

DBMS_XMLDOM.FREEELEMENT

DBE_XMLDOM.FREEELEMENT

-

6

DBMS_XMLDOM.FREENODE

DBE_XMLDOM.FREENODE

-

7

DBMS_XMLDOM.FREENODELIST

DBE_XMLDOM.FREENODELIST

GaussDB: The nodelist will be released.

Oracle Database: After the nodelist is released, it can still be queried in the original document.

8

DBMS_XMLDOM.GETATTRIBUTE

DBE_XMLDOM.GETATTRIBUTE

-

9

DBMS_XMLDOM.GETATTRIBUTES

DBE_XMLDOM.GETATTRIBUTES

-

10

DBMS_XMLDOM.GETCHILDNODES

DBE_XMLDOM.GETCHILDNODES

GaussDB: When the document node is used, DTD is included.

Oracle Database: DTD is not included.

11

DBMS_XMLDOM.GETCHILDRENBYTAGNAME

DBE_XMLDOM.GETCHILDRENBYTAGNAME

GaussDB: The ns parameter of the DBE_XMLDOM.GETCHILDRENBYTAGNAME API does not support the asterisk (*) parameter. To obtain all attributes of a node, use the DBE_XMLDOM.GETCHILDNODES API.

Oracle Database: The input parameter * is supported.

12

DBMS_XMLDOM.GETDOCUMENTELEMENT

DBE.XMLDOM.GETDOCUMENTELEMENT

-

13

DBMS_XMLDOM.GETFIRSTCHILD

DBE_XMLDOM.GETFIRSTCHILD

-

14

DBMS_XMLDOM.GETLASTCHILD

DBE_XMLDOM.GETLASTCHILD

-

15

DBMS_XMLDOM.GETLENGTH

DBE_XMLDOM.GETLENGTH

-

16

DBMS_XMLDOM.GETLOCALNAME

DBE_XMLDOM.GETLOCALNAME

-

17

DBMS_XMLDOM.GETNAMEDITEM

DBE_XMLDOM.GETNAMEDITEM

-

18

DBMS_XMLDOM.GETNEXTSIBLING

DBE_XMLDOM.GETNEXTSIBLING

-

19

DBMS_XMLDOM.GETNODENAME

DBE_XMLDOM.GETNODENAME

-

20

DBMS_XMLDOM.GETNODETYPE

DBE_XMLDOM.GETNODETYPE

-

21

DBMS_XMLDOM.GETTAGNAME

DBE_XMLDOM.GETTAGNAME

-

22

DBMS_XMLDOM.IMPORTNODE

DBE_XMLDOM.IMPORTNODE

-

23

DBMS_XMLDOM.ISNULL

DBE_XMLDOM.ISNULL

GaussDB: When the input parameter is of the DOMNODELIST type, an error is reported if the object does not exist in the hash table.

Oracle Database: No error is reported.

24

DBMS_XMLDOM.ITEM

DBE_XMLDOM.ITEM

-

25

DBMS_XMLDOM.MAKENODE

DBE_XMLDOM.MAKENODE

GaussDB: This function cannot be directly returned as the function return value.

Oracle Database: It is directly returned as the function return value.

26

DBMS_XMLDOM.NEWDOMDOCUMENT

DBE_XMLDOM.NEWDOMDOCUMENT
  • The input parameter size in GaussDB must be less than 2 GB.

    Oracle Database: The size is the same as that of the CLOB type.

  • Currently, external DTD parsing is not supported in GaussDB.

    Oracle Database: External DTD can be parsed.

  • GaussDB: The default character set of doc created by newdomdocument is UTF-8.

    Oracle Database: It is generated based on the character set of the server.

  • GaussDB: Each doc parsed from the same xmltype instance is independent, and the modification of the doc does not affect the xmltype.

    Oracle Database: Each doc parsed from the same xmltype instance is not independent but associated.

  • GaussDB: The version column supports only 1.0. If 1.0 to 1.9 are parsed, a warning is reported but the execution is normal. For versions later than 1.9, an error is reported.

    Oracle Database: No error is reported.

  • DTD verification difference between GaussDB and Oracle Database: !ATTLIST to type (CHECK|check|Check) "Ch..." reports an error because the default value "Ch..." is not an enumerated value in the brackets. However, Oracle Database does not report this error. <!ENTITY baidu "www.baidu.com">...... &Baidu;&writer reports an error. Baidu cannot correspond to baidu because the letters are case-sensitive.

    Oracle Database: No error is reported.

  • Namespace verification difference between GaussDB and Oracle Database: Undeclared namespace tags are parsed in GaussDB.

    Oracle Database: An error is reported.

27

DBMS_XMLDOM.SETATTRIBUTE

DBE_XMLDOM.SETATTRIBUTE

GaussDB: The attribute key cannot be null or an empty string.

Oracle Database: The attribute key can be null or an empty string.

28

DBMS_XMLDOM.SETCHARSET

DBE_XMLDOM.SETCHARSET

Currently, the following character sets are supported in GaussDB: UTF-8, UTF-16, UCS-4, UCS-2, ISO-8859-1, ISO-8859-2, ISO-8859-3, ISO-8859-4, ISO-8859-5, ISO-8859-6, ISO-8859-7, ISO-8859-8, ISO-8859-9, ISO-2022-JP, Shift_JIS, EUC-JP, and ASCII. If you enter other character sets, an error is reported or garbled characters may be displayed.

29

DBMS_XMLDOM.SETDOCTYPE

DBE_XMLDOM.SETDOCTYPE

GaussDB: The total length of name, sysid, and pubid cannot exceed 32,500 bytes.

Oracle Database: The maximum size is 32,767 bytes.

30

DBMS_XMLDOM.WRITETOBUFFER

DBE_XMLDOM.WRITETOBUFFER
  • GaussDB: The writetobuffer output buffer is limited to less than 1 GB.

    Oracle Database: The maximum size is 32,767 bytes.

  • GaussDB: The output doc will contain the XML declaration version and encoding.

    Oracle Database: It is not contained unless being specified by users.

  • GaussDB: If the input parameter is of the domnode type and the node is converted from a doc, the output node contains the XML declaration version and encoding.

    Oracle Database: It is not contained unless being specified by users.

  • GaussDB: By default, XML files are output in the UTF-8 character set.

    Oracle Database: It is generated based on the database character set.

31

DBMS_XMLDOM.WRITETOCLOB

DBE_XMLDOM.WRITETOCLOB
  • GaussDB: The writetoclob size cannot exceed 1 GB.

    Oracle Database: The supported size depends on the CLOB size.

  • GaussDB: The output doc will contain the XML declaration version and encoding.

    Oracle Database: It is not contained unless being specified by users.

  • GaussDB: If the input parameter is of the domnode type and the node is converted from a doc, the output node contains the XML declaration version and encoding.

    Oracle Database: It is not contained unless being specified by users.

  • GaussDB: By default, XML files are output in the UTF-8 character set.

    Oracle Database: It is generated based on the database character set.

32

DBMS_XMLDOM.WRITETOFILE

DBE_XMLDOM.WRITETOFILE
  • GaussDB document input parameter. The length of filename cannot exceed 255 bytes. For details about charset, see the dbe_xmldom.setcharset API.

    Oracle Database: The length of filename is affected by the OS and is greater than 255 bytes.

  • GaussDB DOMNode input parameter. The length of filename cannot exceed 255 bytes. For details about charset, see the dbe_xmldom.setcharset API.

    Oracle Database: The length of filename is affected by the OS and is greater than 255 bytes.

  • GaussDB: This function adds content such as indentation to format the output. The output doc will contain the XML declaration version and encoding. If the input parameter is of the domnode type and the node is converted from a doc, the output node contains the XML declaration version and encoding.

    Oracle Database: It is not contained unless being specified by users.

  • GaussDB: If newdomdocument() is used to create a doc without parameters, no error is reported when charset is not specified. The UTF-8 character set is used by default.

    Oracle Database: An error is reported.

  • GaussDB: The filename must be in the path created in pg_directory. The backslash (\) in the filename will be converted to a slash (/). Only one slash (/) is allowed. The file name must be in the pg_directory_name/file_name format.

    Oracle Database: User input is not escaped.

33

DBMS_XMLDOM.GETNODEVALUE

DBE_XMLDOM.GETNODEVALUE

-

34

DBMS_XMLDOM.GETPARENTNODE

DBE_XMLDOM.GETPARENTNODE

-

35

DBMS_XMLDOM.HASCHILDNODES

DBE_XMLDOM.HASCHILDNODES

-

36

DBMS_XMLDOM.MAKEELEMENT

DBE_XMLDOM.MAKEELEMENT

-

37

DBMS_XMLDOM.SETNODEVALUE

DBE_XMLDOM.SETNODEVALUE
  • GaussDB: Input parameter of nodeValue. You can enter an empty string or NULL, but the node value will not be changed.

    Oracle Database: If you enter an empty string or NULL, the node value is set to an empty string.

  • GaussDB: Input parameter of nodeValue. The escape character '&' is not supported. If the character string contains the escape character, the node value will be cleared.

    Oracle Database: Escape characters are supported.

38

DBMS_XMLDOM.GETELEMENTSBYTAGNAME

DBE_XMLDOM.GETELEMENTSBYTAGNAME

-
Table 15 DBMS_XMLPARSER compatibility

No.

Oracle Database

GaussDB

Difference

1

DBMS_XMLPARSER.FREEPARSER

DBE_XMLPARSER.FREEPARSER

-

2

DBMS_XMLPARSER.GETDOCUMENT

DBE_XMLPARSER.GETDOCUMENT

-

3

DBMS_XMLPARSER.GETVALIDATIONMODE

DBE_XMLPARSER.GETVALIDATIONMODE

-

4

DBMS_XMLPARSER.NEWPARSER

Supported, with differences in DBE_XMLPARSER.NEWPARSER

The maximum number of parser objects in GaussDB is 16,777,215, and that in Oracle Database is about 100 million.

5

DBMS_XMLPARSER.PARSEBUFFER

Supported, with differences in DBE_XMLPARSER.PARSEBUFFER

1. Difference in parsing columns:

Only UTF-8 is supported in terms of character encoding, and version can only be set to 1.0. If versions 1.0 to 1.9 are parsed, a warning appears but the execution is normal. For versions later than 1.9, an error is reported.

2. Namespace validation difference: Undeclared namespace tags are parsed. However, Oracle Database reports an error.

3. Difference in parsing XML predefined entities: &apos; and &quot; are parsed and translated into ' and ". However, predefined entities in Oracle Database are not translated into characters.

4. DTD validation differences:
  • !ATTLIST to type (CHECK|check|Check) "Ch..." reports an error because the default value "Ch..." is not an enumerated value in the brackets. However, Oracle Database does not report this error.
  • <!ENTITY baidu "www.baidu.com">...... &Baidu;&writer reports an error because the letters are case-sensitive. Baidu cannot correspond to baidu. However, Oracle Database does not report this error.

6

DBMS_XMLPARSER.PARSECLOB

Supported, with differences in DBE_XMLPARSER.PARSECLOB

1. PARSECLOB cannot parse CLOBs greater than or equal to 2 GB.

2. Difference in parsing columns:

Only UTF-8 is supported in terms of character encoding, and version can only be set to 1.0. If versions 1.0 to 1.9 are parsed, a warning appears but the execution is normal. For versions later than 1.9, an error is reported.

3. Namespace validation difference: Undeclared namespace tags are parsed. However, Oracle Database reports an error.

4. Difference in parsing XML predefined entities: &apos; and &quot; are parsed and translated into ' and ". However, predefined entities in Oracle Database are not translated into characters.

5. DTD validation differences:
  • !ATTLIST to type (CHECK|check|Check) "Ch..." reports an error because the default value "Ch..." is not an enumerated value in the brackets. However, Oracle Database does not report this error.
  • <!ENTITY baidu "www.baidu.com">...... &Baidu;&writer reports an error because the letters are case-sensitive. Baidu cannot correspond to baidu. However, Oracle Database does not report this error.

7

DBMS_XMLPARSER.SETVALIDATIONMODE

DBE_XMLPARSER.SETVALIDATIONMODE

-
Table 16 DBMS_ILM compatibility

No.

Oracle Database

GaussDB

Difference

1

DBMS_ILM.ADD_TO_ILM

Not supported.

-

2

DBMS_ILM.ARCHIVESTATENAME

Not supported.

-

3

DBMS_ILM.EXECUTE_ILM

Supported, with differences in DBE_ILM.EXECUTE_ILM
  • The input parameter schema in GaussDB corresponds to owner in Oracle Database.
  • GaussDB does not support the operation of specifying ilm_scope (specifying multiple objects at a time).

4

DBMS_ILM.EXECUTE_ILM_TASK

Not supported.

-

5

DBMS_ILM.PREVIEW_ILM

Not supported.

-

6

DBMS_ILM.REMOVE_FROM_ILM

Not supported.

-

7

DBMS_ILM.STOP_ILM

DBE_ILM.STOP_ILM

-
Table 17 DBMS_ILM_ADMIN compatibility

No.

Oracle Database

GaussDB

Difference

1

DBMS_ILM_ADMIN.CLEAR_HEAT_MAP_ALL

Not supported.

-

2

DBMS_ILM_ADMIN.CLEAR_HEAT_MAP_TABLE

Not supported.

-

3

DBMS_ILM_ADMIN.CUSTOMIZE_ILM

Supported, with differences in DBE_ILM_ADMIN.CUSTOMIZE_ILM

The feature parameters corresponding to the values of input parameters are different. The value of param in GaussDB can be 1, 2, 7, 11, 12, 13, 14, or 15. When the value of param in GaussDB is 14, the corresponding feature parameter is WIND_DURATION which is used to control the execution window duration in automatic scheduling. When the value of param in Oracle Database is 14, the corresponding feature parameter is AUTO_OPTIMIZE_INACTIVITY_THRESHOLD which indicates the inactive duration of the ADO.

4

DBMS_ILM_ADMIN.DISABLE_ILM

DBE_ILM_ADMIN.DISABLE_ILM

-

5

DBMS_ILM_ADMIN.ENABLE_AUTO_OPTIMIZE

Not supported.

-

6

DBMS_ILM_ADMIN.ENABLE_ILM

DBE_ILM_ADMIN.ENABLE_ILM

-

7

DBMS_ILM_ADMIN.

IGNORE_AUTO_OPTIMIZE_

CRITERIA

Not supported.

-

8

DBMS_ILM_ADMIN.SET_HEAT_MAP_ALL

Not supported.

-

9

DBMS_ILM_ADMIN.SET_HEAT_MAP_START

Not supported.

-

10

DBMS_ILM_ADMIN.SET_HEAT_MAP_TABLE

Not supported.

-
Table 18 DBMS_COMPRESSION compatibility

No.

Oracle Database

GaussDB

Difference

1

DBMS_COMPRESSION.GET_COMPRESSION_RATIO

Supported, with differences in DBE_COMPRESSION.GET_COMPRESSION_RATIO
  • GaussDB cannot obtain compression rates of LOBs.
  • For obtaining a compression rate of a single object:
    • The value of the input parameter comptype in GaussDB can only be 1 (uncompressed) or 2 (advanced compression) while Oracle Database also supports values such as 1024 and 2048.
    • The value of the input parameter objtype in GaussDB can only be 1 (table object) while Oracle Database also supports the value 2 (index object).
    • Oracle Database uses the subset_numrows parameter to directly determine the number of rows to be sampled (that is, the value of the parameter). GaussDB uses sample_ratio (sampling rate) to indirectly determine the number of rows to be sampled.

2

DBMS_COMPRESSION.GET_COMPRESSION_TYPE

Supported, with differences in DBE_COMPRESSION.GET_COMPRESSION_TYPE
  • Oracle Database uses a row ID to specify the row whose compression type is to be obtained, while GaussDB uses a CTID to specify the row.
  • The value of comptype is returned. The value difference is the same as that of GET_COMPRESSION_RATIO.
Table 19 DBMS_HEAT_MAP compatibility

No.

Oracle Database

GaussDB

Difference

1

DBMS_HEAT_MAP.BLOCK_HEAT_MAP

Not supported.

-

2

DBMS_HEAT_MAP.EXTENT_HEAT_MAP

Not supported.

-

3

DBMS_HEAT_MAP.OBJECT_HEAT_MAP

Not supported.

-

4

DBMS_HEAT_MAP.SEGMENT_HEAT_MAP

Not supported.

-

5

DBMS_HEAT_MAP.TABLESPACE_HEAT_MAP

Not supported.

-

6

Not supported.

DBE_HEAT_MAP.ROW_HEAT_MAP

For details, see "Stored Procedure > Advanced Package > Secondary Encapsulation Interfaces (Recommended) > DBE_HEAT_MAP" in Developer Guide.
Table 20 DBMS_DESCRIBE compatibility

No.

Oracle Database

GaussDB

Difference

1

DBMS_DESCRIBE.DESCRIBE_PROCEDURE

Supported, with differences in DBE_DESCRIBE.DESCRIBE_PROCEDURE
  • The datatype parameter is different from the O database. GaussDB returns the OID of the data type, and the O database returns the ID of the data type in the O database.
  • The datalength, dataprecision, and scale parameters are set to 0 because type constraints (such as number (7,2) and varchar2(20)) cannot be retained when GaussDB creates stored procedures or functions. Oracle Database can use the %type method to obtain constrained data types.
  • For details about the behavior differences, see "Stored Procedure > Advanced Package > Secondary Encapsulation Interfaces (Recommended) > DBE_DESCRIBE" in Developer Guide.
Table 21 DBMS_STATS compatibility

No.

Oracle Database

GaussDB

Difference

1

DBMS_STATS.ALTER_STATS_HISTORY_RETENTION

Not supported.

-

2

DBMS_STATS.CANCEL_ADVISOR_TASK

Not supported.

-

3

DBMS_STATS.CONFIGURE_ADVISOR_FILTER

Not supported.

-

4

DBMS_STATS.CONFIGURE_ADVISOR_OBJ_FILTER

Not supported.

-

5

DBMS_STATS.CONFIGURE_ADVISOR_OPR_FILTER

Not supported.

-

6

DBMS_STATS.CONFIGURE_ADVISOR_RULE_FILTER

Not supported.

-

7

DBMS_STATS.CREATE_ADVISOR_TASK

Not supported.

-

8

DBMS_STATS.CONVERT_RAW_VALUE

Not supported.

-

9

DBMS_STATS.CONVERT_RAW_VALUE_NVARCHAR

Not supported.

-

10

DBMS_STATS.CONVERT_RAW_VALUE_ROWID

Not supported.

-

11

DBMS_STATS.COPY_TABLE_STATS

Not supported.

-

12

DBMS_STATS.CREATE_EXTENDED_STATS

Not supported.

-

13

DBMS_STATS.CREATE_STAT_TABLE

DBE_STATS.CREATE_STAT_TABLE
  • In GaussDB, ownname must be set to a schema name.
  • GaussDB supports only some input parameter functions. For details, see "Stored Procedure > Advanced Package > Secondary Encapsulation Interfaces (Recommended) > DBE_STATS" in Developer Guide.

14

DBMS_STATS.DELETE_COLUMN_STATS

DBE_STATS.DELETE_COLUMN_STATS
  • In GaussDB, ownname must be set to a schema name.
  • GaussDB supports only some input parameter functions. For details, see "Stored Procedure > Advanced Package > Secondary Encapsulation Interfaces (Recommended) > DBE_STATS" in Developer Guide.
  • In GaussDB, this API can be used to set expression statistics, but tabname must be set to an index name corresponding to the expression.

15

DBMS_STATS.DELETE_DATABASE_PREFS

Not supported.

-

16

DBMS_STATS.DELETE_DATABASE_STATS

Not supported.

-

17

DEDBMS_STATS.DELETE_DICTIONARY_STATS

Not supported.

-

18

DBMS_STATS.DELETE_FIXED_OBJECTS_STATS

Not supported.

-

19

DBMS_STATS.DELETE_INDEX_STATS

DBE_STATS.DELETE_INDEX_STATS
  • In GaussDB, ownname must be set to a schema name.
  • GaussDB supports only some input parameter functions. For details, see "Stored Procedure > Advanced Package > Secondary Encapsulation Interfaces (Recommended) > DBE_STATS" in Developer Guide.

20

DBMS_STATS.DELETE_PENDING_STATS

Not supported.

-

21

DBMS_STATS.DELETE_PROCESSING_RATE

Not supported.

-

22

DBMS_STATS.DELETE_SCHEMA_PREFS

Not supported.

-

23

DBMS_STATS.DELETE_SCHEMA_STATS

DBE_STATS.DELETE_SCHEMA_STATS
  • In GaussDB, ownname must be set to a schema name.
  • GaussDB supports only some input parameter functions. For details, see "Stored Procedure > Advanced Package > Secondary Encapsulation Interfaces (Recommended) > DBE_STATS" in Developer Guide.

24

DBMS_STATS.DELETE_SYSTEM_STATS

Not supported.

-

25

DBMS_STATS.DELETE_TABLE_PREFS

Not supported.

-

26

DBMS_STATS.DELETE_TABLE_STATS

DBE_STATS.DELETE_TABLE_STATS
  • In GaussDB, ownname must be set to a schema name.
  • GaussDB supports only some input parameter functions. For details, see "Stored Procedure > Advanced Package > Secondary Encapsulation Interfaces (Recommended) > DBE_STATS" in Developer Guide.

27

DBMS_STATS.DIFF_TABLE_STATS_IN_HISTORY

Not supported.

-

28

DBMS_STATS.DIFF_TABLE_STATS_IN_PENDING

Not supported.

-

29

DBMS_STATS.DIFF_TABLE_STATS_IN_STATTAB

Not supported.

-

30

DBMS_STATS.DROP_ADVISOR_TASK

Not supported.

-

31

DBMS_STATS.DROP_EXTENDED_STATS

Not supported.

-

32

DBMS_STATS.DROP_STAT_TABLE

DBE_STATS.DROP_STAT_TABLE

-

33

DBMS_STATS.EXECUTE_ADVISOR_TASK

Not supported.

-

34

DBMS_STATS.EXPORT_COLUMN_STATS

DBE_STATS.EXPORT_COLUMN_STATS
  • In GaussDB, ownname must be set to a schema name.
  • GaussDB supports only some input parameter functions. For details, see "Stored Procedure > Advanced Package > Secondary Encapsulation Interfaces (Recommended) > DBE_STATS" in Developer Guide.
  • The exported column-level statistics are consistent with those in the pg_statistic catalog. Multiple columns are consistent with those in the pg_statistic_ext catalog.
  • Index expression statistics can be exported. tabname must be set to an index name, and colname must be set to an index expression name.
  • Permission: You must have the analyze permission to query tables and the siud permission on the stattab table.

35

DBMS_STATS.EXPORT_DATABASE_PREFS

Not supported.

-

36

DBMS_STATS.EXPORT_DATABASE_STATS

Not supported.

-

37

DBMS_STATS.EXPORT_DICTIONARY_STATS

Not supported.

-

38

DBMS_STATS.EXPORT_FIXED_OBJECTS_STATS

Not supported.

-

39

DBMS_STATS.EXPORT_INDEX_STATS

DBE_STATS.EXPORT_INDEX_STATS
  • In GaussDB, ownname must be set to a schema name.
  • GaussDB supports only some input parameter functions. For details, see "Stored Procedure > Advanced Package > Secondary Encapsulation Interfaces (Recommended) > DBE_STATS" in Developer Guide.
  • In the stattab table, the exported table-level and partition-level statistics are numrows, numblocks, and relallvisible, which correspond to reltuples, relpages, and relallvisible in the pg_class and pg_partition system catalogs, respectively.
  • Permission: You must have the analyze permission to query tables and the siud permission on the stattab table.

40

DBMS_STATS.EXPORT_PENDING_STATS

Not supported.

-

41

DBMS_STATS.EXPORT_SCHEMA_PREFS

Not supported.

-

42

DBMS_STATS.EXPORT_SCHEMA_STATS

DBE_STATS.EXPORT_SCHEMA_STATS
  • In GaussDB, ownname must be set to a schema name.
  • GaussDB supports only some input parameter functions. For details, see "Stored Procedure > Advanced Package > Secondary Encapsulation Interfaces (Recommended) > DBE_STATS" in Developer Guide.
  • In the stattab table, the exported table-level and partition-level statistics are numrows, numblocks, and relallvisible, which correspond to reltuples, relpages, and relallvisible in the pg_class and pg_partition system catalogs, respectively. The column-level statistics of the exported table are consistent with those of the pg_statistic and pg_statistic_ext catalogs.
  • Permission: You must have the siud permission on the stattab table.

43

DBMS_STATS.EXPORT_SYSTEM_STATS

Not supported.

-

44

DBMS_STATS.EXPORT_TABLE_PREFS

Not supported.

-

45

DBMS_STATS.EXPORT_TABLE_STATS

DBE_STATS.EXPORT_TABLE_STATS
  • In GaussDB, ownname must be set to a schema name.
  • GaussDB supports only some input parameter functions. For details, see "Stored Procedure > Advanced Package > Secondary Encapsulation Interfaces (Recommended) > DBE_STATS" in Developer Guide.
  • In the stattab table, the exported table-level and partition-level statistics are numrows, numblocks, and relallvisible, which correspond to reltuples, relpages, and relallvisible in the pg_class and pg_partition system catalogs, respectively. The column-level statistics exported in cascading mode are consistent with those in the pg_statistic and pg_statistic_ext catalogs.
  • Permission: You must have the analyze permission to query tables and the siud permission on the stattab table.

46

DBMS_STATS.FLUSH_DATABASE_MONITORING_INFO

Not supported.

-

47

DBMS_STATS.GATHER_DATABASE_STATS

Not supported.

-

48

DBMS_STATS.GATHER_DICTIONARY_STATS

Not supported.

-

49

DBMS_STATS.GATHER_FIXED_OBJECTS_STATS

Not supported.

-

50

DBMS_STATS.GATHER_INDEX_STATS

Not supported.

-

51

DBMS_STATS.GATHER_PROCESSING_RATE

Not supported.

-

52

DBMS_STATS.GATHER_SCHEMA_STATS

Not supported.

-

53

DBMS_STATS.GATHER_SYSTEM_STATS

Not supported.

-

54

DBMS_STATS.GATHER_TABLE_STATS

Not supported.

-

55

DBMS_STATS.GENERATE_STATS

Not supported.

-

56

DBMS_STATS.GET_ADVISOR_OPR_FILTER

Not supported.

-

57

DBMS_STATS.GET_ADVISOR_RECS

Not supported.

-

58

DBMS_STATS.GET_COLUMN_STATS

Not supported.

-

59

DBMS_STATS.GET_INDEX_STATS

Not supported.

-

60

DBMS_STATS.GET_PARAM

Not supported.

-

61

DBMS_STATS.GET_PREFS

Not supported.

-

62

DBMS_STATS.GET_STATS_HISTORY_AVAILABILITY

DBE_STATS.GET_STATS_HISTORY_AVAILABILITY

GaussDB queries the collection time of the earliest historical statistics in the entire database.

63

DBMS_STATS.GET_STATS_HISTORY_RETENTION

DBE_STATS.GET_STATS_HISTORY_RETENTION

-

64

DBMS_STATS.GET_SYSTEM_STATS

Not supported.

-

65

DBMS_STATS.GET_TABLE_STATS

Not supported.

-

66

DBMS_STATS.IMPLEMENT_ADVISOR_TASK

Not supported.

-

67

DBMS_STATS.IMPORT_COLUMN_STATS

DBE_STATS.IMPORT_COLUMN_STATS
  • In GaussDB, ownname must be set to a schema name.
  • GaussDB supports only some input parameter functions. For details, see "Stored Procedure > Advanced Package > Secondary Encapsulation Interfaces (Recommended) > DBE_STATS" in Developer Guide.
  • The exported single-column col statistics are the same as those in the pg_statistic catalog. The exported multi-column ext-col statistics are consistent with those in the pg_statistic_ext catalog.
  • Index expression statistics can be imported. tabname must be set to an index name, and colname must be set to an index expression name.
  • Permission: You must have the analyze permission to query tables and the siud permission on the stattab table.

68

DBMS_STATS.IMPORT_DATABASE_PREFS

Not supported.

-

69

DBMS_STATS.IMPORT_DATABASE_STATS

Not supported.

-

70

DBMS_STATS.IMPORT_DICTIONARY_STATS

Not supported.

-

71

DBMS_STATS.IMPORT_FIXED_OBJECTS_STATS

Not supported.

-

72

DBMS_STATS.IMPORT_INDEX_STATS

DBE_STATS.IMPORT_INDEX_STATS
  • In GaussDB, ownname must be set to a schema name.
  • GaussDB supports only some input parameter functions. For details, see "Stored Procedure > Advanced Package > Secondary Encapsulation Interfaces (Recommended) > DBE_STATS" in Developer Guide.
  • In the stattab table, the imported table-level and partition-level statistics are numrows, numblocks, and relallvisible, which correspond to reltuples, relpages, and relallvisible in the pg_class and pg_partition system catalogs, respectively.
  • Permission: You must have the analyze permission to query tables and the siud permission on the stattab table.

73

DBMS_STATS.IMPORT_SCHEMA_PREFS

Not supported.

-

74

DBMS_STATS.IMPORT_SCHEMA_STATS

DBE_STATS.IMPORT_SCHEMA_STATS
  • In GaussDB, ownname must be set to a schema name.
  • GaussDB supports only some input parameter functions. For details, see "Stored Procedure > Advanced Package > Secondary Encapsulation Interfaces (Recommended) > DBE_STATS" in Developer Guide.
  • In the stattab table, the imported table-level and partition-level statistics are numrows, numblocks, and relallvisible, which correspond to reltuples, relpages, and relallvisible in the pg_class and pg_partition system catalogs, respectively. The column-level statistics of the imported table are consistent with those of the pg_statistic and pg_statistic_ext catalogs.
  • Permission: You must have the siud permission on the stattab table.

75

DBMS_STATS.IMPORT_SYSTEM_STATS

Not supported.

-

76

DBMS_STATS.IMPORT_TABLE_PREFS

Not supported.

-

77

DBMS_STATS.IMPORT_TABLE_STATS

DBE_STATS.IMPORT_TABLE_STATS
  • In GaussDB, ownname must be set to a schema name.
  • GaussDB supports only some input parameter functions. For details, see "Stored Procedure > Advanced Package > Secondary Encapsulation Interfaces (Recommended) > DBE_STATS" in Developer Guide.
  • In the stattab table, the imported table-level and partition-level statistics are numrows, numblocks, and relallvisible, which correspond to reltuples, relpages, and relallvisible in the pg_class and pg_partition system catalogs, respectively. The column-level statistics imported in cascading mode are consistent with those in the pg_statistic and pg_statistic_ext catalogs.
  • Permission: You must have the analyze permission to query tables and the siud permission on the stattab table.

78

DBMS_STATS.INTERRUPT_ADVISOR_TASK

Not supported.

-

79

DBMS_STATS.LOCK_PARTITION_STATS

DBE_STATS.LOCK_PARTITION_STATS

In GaussDB, ownname must be set to a schema name.

80

DBMS_STATS.LOCK_SCHEMA_STATS

DBE_STATS.LOCK_SCHEMA_STATS

In GaussDB, ownname must be set to a schema name.

81

DBMS_STATS.LOCK_TABLE_STATS

DBE_STATS.LOCK_TABLE_STATS

In GaussDB, ownname must be set to a schema name.

82

DBMS_STATS.MERGE_COL_USAGE

Not supported.

-

83

DBMS_STATS.PREPARE_COLUMN_VALUES

Not supported.

-

84

DBMS_STATS.PREPARE_COLUMN_VALUES_ROWID

Not supported.

-

85

DBMS_STATS.PUBLISH_PENDING_STATS

Not supported.

-

86

DBMS_STATS.PURGE_STATS

DBE_STATS.PURGE_STATS

-

87

DBMS_STATS.REMAP_STAT_TABLE

Not supported.

-

88

DBMS_STATS.REPORT_ADVISOR_TASK

Not supported.

-

89

DBMS_STATS.REPORT_COL_USAGE

Not supported.

-

90

DBMS_STATS.REPORT_GATHER_AUTO_STATS

Not supported.

-

91

DBMS_STATS.REPORT_GATHER_DATABASE_STATS

Not supported.

-

92

DBMS_STATS.REPORT_GATHER_DICTIONARY_STATS

Not supported.

-

93

DBMS_STATS.REPORT_GATHER_FIXED_OBJ_STATS

Not supported.

-

94

DBMS_STATS.REPORT_GATHER_SCHEMA_STATS

Not supported.

-

95

DBMS_STATS.REPORT_STATS_OPERATIONS

Not supported.

-

96

DBMS_STATS.RESET_ADVISOR_TASK

Not supported.

-

97

DBMS_STATS.RESET_COL_USAGE

Not supported.

-

98

DBMS_STATS.RESET_GLOBAL_PREF_DEFAULTS

Not supported.

-

99

DBMS_STATS.RESET_PARAM_DEFAULTS

Not supported.

-

100

DBMS_STATS.RESTORE_DICTIONARY_STATS

Not supported.

-

101

DBMS_STATS.RESTORE_FIXED_OBJECTS_STATS

Not supported.

-

102

DBMS_STATS.RESTORE_SCHEMA_STATS

DBE_STATS.RESTORE_SCHEMA_STATS
  • In GaussDB, ownname must be set to a schema name.
  • GaussDB supports only some input parameter functions. For details, see "Stored Procedure > Advanced Package > Secondary Encapsulation Interfaces (Recommended) > DBE_STATS" in Developer Guide.

103

DBMS_STATS.RESTORE_SYSTEM_STATS

Not supported.

-

104

DBMS_STATS.RESTORE_TABLE_STATS

DBE_STATS.RESTORE_TABLE_STATS
  • In GaussDB, ownname must be set to a schema name.
  • GaussDB supports only some input parameter functions. For details, see "Stored Procedure > Advanced Package > Secondary Encapsulation Interfaces (Recommended) > DBE_STATS" in Developer Guide.

105

DBMS_STATS.RESUME_ADVISOR_TASK

Not supported.

-

106

DBMS_STATS.SCRIPT_ADVISOR_TASK

Not supported.

-

107

DBMS_STATS.SEED_COL_USAGE

Not supported.

-

108

DBMS_STATS.SET_ADVISOR_TASK_PARAMETER

Not supported.

-

109

DBMS_STATS.SET_COLUMN_STATS

DBE_STATS.SET_COLUMN_STATS
  • In GaussDB, ownname must be set to a schema name.
  • GaussDB supports only some input parameter functions. For details, see "Stored Procedure > Advanced Package > Secondary Encapsulation Interfaces (Recommended) > DBE_STATS" in Developer Guide.

110

DBMS_STATS.SET_DATABASE_PREFS

Not supported.

-

111

DBMS_STATS.SET_GLOBAL_PREFS

Not supported.

-

112

DBMS_STATS.SET_INDEX_STATS

DBE_STATS.SET_INDEX_STATS
  • In GaussDB, ownname must be set to a schema name.
  • GaussDB supports only some input parameter functions. For details, see "Stored Procedure > Advanced Package > Secondary Encapsulation Interfaces (Recommended) > DBE_STATS" in Developer Guide.
  • The relallvisible input parameter is added to GaussDB.

113

DBMS_STATS.SET_PARAM

Not supported.

-

114

DBMS_STATS.SET_PROCESSING_RATE

Not supported.

-

115

DBMS_STATS.SET_SCHEMA_PREFS

Not supported.

-

116

DBMS_STATS.SET_SYSTEM_STATS

Not supported.

-

117

DBMS_STATS.SET_TABLE_PREFS

Not supported.

-

118

DBMS_STATS.SET_TABLE_STATS

DBE_STATS.SET_TABLE_STATS
  • In GaussDB, ownname must be set to a schema name.
  • GaussDB supports only some input parameter functions. For details, see "Stored Procedure > Advanced Package > Secondary Encapsulation Interfaces (Recommended) > DBE_STATS" in Developer Guide.
  • The relallvisible input parameter is added to GaussDB.

119

DBMS_STATS.SHOW_EXTENDED_STATS_NAME

Not supported.

-

120

DBMS_STATS.TRANSFER_STATS

Not supported.

-

121

DBMS_STATS.UNLOCK_PARTITION_STATS

DBE_STATS.UNLOCK_PARTITION_STATS

In GaussDB, ownname must be set to a schema name.

122

DBMS_STATS.UNLOCK_SCHEMA_STATS

DBE_STATS.UNLOCK_SCHEMA_STATS

In GaussDB, ownname must be set to a schema name.

123

DBMS_STATS.UNLOCK_TABLE_STATS

DBE_STATS.UNLOCK_TABLE_STATS

In GaussDB, ownname must be set to a schema name.

124

DBMS_STATS.UPGRADE_STAT_TABLE

Not supported.

-
Table 22 DBMS_XMLGEN compatibility

No.

Oracle Database

GaussDB

Difference

1

DBMS_XMLGEN.CONVERT

DBE_XMLGEN.CONVERT

-

2

DBMS_XMLGEN.NEWCONTEXT

DBE_XMLGEN.NEWCONTEXT

-

3

DBMS_XMLGEN.NEWCONTEXTFROMHIERARCHY

DBE_XMLGEN.NEWCONTEXTFROMHIERARCHY
  • The maximum depth of recursive XML files generated by GaussDB cannot exceed 50 million layers.
  • XML files generated by the CONNECT BY statement in Oracle Database's newcontextfromhierarchy method contain XML headers. However, the directly constructed data does not contain the XML header. In GaussDB, the files contain XML headers.

4

DBMS_XMLGEN.SETCONVERTSPECIALCHARS

DBE_XMLGEN.SETCONVERTSPECIALCHARS

-

5

DBMS_XMLGEN.SETNULLHANDLING

DBE_XMLGEN.SETNULLHANDLING

-

6

DBMS_XMLGEN.SETROWSETTAG

DBE_XMLGEN.SETROWSETTAG

-

7

DBMS_XMLGEN.SETROWTAG

DBE_XMLGEN.SETROWTAG

-

8

DBMS_XMLGEN.USENULLATTRIBUTEINDICATOR

DBE_XMLGEN.USENULLATTRIBUTEINDICATOR

-

9

DBMS_XMLGEN.USEITEMTAGSFORCOLL

DBE_XMLGEN.USEITEMTAGSFORCOLL

-

10

DBMS_XMLGEN.GETNUMROWSPROCESSED

DBE_XMLGEN.GETNUMROWSPROCESSED

-

11

DBMS_XMLGEN.SETMAXROWS

DBE_XMLGEN.SETMAXROWS

-

12

DBMS_XMLGEN.SETSKIPROWS

DBE_XMLGEN.SETSKIPROWS

-

13

DBMS_XMLGEN.RESTARTQUERY

DBE_XMLGEN.RESTARTQUERY
  • GaussDB: The updated data is invisible after the RESTARTQUERY method is called.
  • Oracle Database: The updated data is visible after the RESTARTQUERY method is called.

14

DBMS_XMLGEN.GETXMLTYPE

DBE_XMLGEN.GETXMLTYPE

-

15

DBMS_XMLGEN.GETXML

DBE_XMLGEN.GETXML

-

16

DBMS_XMLGEN.CLOSECONTEXT

DBE_XMLGEN.CLOSECONTEXT

-
Parent topic: Centralized Instances