cancel
Showing results for 
Search instead for 
Did you mean: 

The identifier that starts with '@skip_compact_extents_reorg_st' is too long. Maximum length is 30

ganimede_dignan
Contributor
0 Kudos

Hi,

I've just upgrade my produktive system from 15.7.0.121 to 15.7.0.136, it's all OK but some reorg jobs end with errors:

Job execution failed. See job history and log file for details.

----------------------------------------------
starting job execution at 2016-10-16 10:30:52
(1 row affected)
The identifier that starts with '@skip_compact_extents_reorg_st' is too long. Maximum length is 30.
The identifier that starts with '@skip_compact_extents_reorg_st' is too long. Maximum length is 30.
Execution of procedure SP_ADM_REORG failed because of errors parsing the source text in syscomments during upgrade. Please drop and recreate dbo.SP_ADM_REORG.

I? also already try to drop the job definition and then re-create again... but not solution.

The job was created as:

Have you got any idea?

Thank you.

ganimede_dignan
Contributor
0 Kudos

No... how can I do it?

Mark_A_Parsons
Contributor
0 Kudos

You could extract the code using ddlgen, then apply the resulting SQL against Sybase (the SQL generated by ddlgen should include drop/create proc and grant commands).

Alternatively, find the script/package that contains the source code for SP_ADM_REORG and extract the code from said source.

NOTE: If this Sybase instance is supporting a SAP application then there may be a SAP note about this type of issue; I don't work with SAP so someone else would need to provide details on such a note.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi there,

I had the same issue today and this is how I fixed it:

1> dbcc upgrade_object (saptools, "SP_ADM_REORG")
2> go

I hope this helps.

Regards,
John