Java ORA-02289:序列不存在,但数据库中不存在序列
我一直在从事一个JavaSpring项目,在该项目中,我创建了一个类,其唯一目的是记录数据库中调用的每个服务的请求体 该表包含名为transaction_id的主键和记录请求所需的其他字段。Java中的表模型如下所示:Java ORA-02289:序列不存在,但数据库中不存在序列,java,spring,oracle,spring-mvc,oracle-sqldeveloper,Java,Spring,Oracle,Spring Mvc,Oracle Sqldeveloper,我一直在从事一个JavaSpring项目,在该项目中,我创建了一个类,其唯一目的是记录数据库中调用的每个服务的请求体 该表包含名为transaction_id的主键和记录请求所需的其他字段。Java中的表模型如下所示: @Entity @Table(name="ForntEndLogHistory") public class FrontEndLog { @Id @Column(name = "TRANSACTION_ID")
@Entity
@Table(name="ForntEndLogHistory")
public class FrontEndLog {
@Id
@Column(name = "TRANSACTION_ID")
@GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "id_generator")
@SequenceGenerator(name="id_generator", sequenceName = "id_seq2", allocationSize=1)
private Long transactionId;
private String request;
}
在数据库中,我创建了一个名为id_seq2的序列,而id_seq1已经存在:
新创建的id\u seq2:
CREATE SEQUENCE "id_seq2" MINVALUE 0 MAXVALUE 9999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ;
commit;
CREATE SEQUENCE "id_seq1" MINVALUE 0 MAXVALUE 9999999999999999999999999999 INCREMENT BY 1 START WITH 3467 NOCACHE NOORDER NOCYCLE ;
已存在id\u seq1 dll:
CREATE SEQUENCE "id_seq2" MINVALUE 0 MAXVALUE 9999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ;
commit;
CREATE SEQUENCE "id_seq1" MINVALUE 0 MAXVALUE 9999999999999999999999999999 INCREMENT BY 1 START WITH 3467 NOCACHE NOORDER NOCYCLE ;
案例1:
CREATE SEQUENCE "id_seq2" MINVALUE 0 MAXVALUE 9999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ;
commit;
CREATE SEQUENCE "id_seq1" MINVALUE 0 MAXVALUE 9999999999999999999999999999 INCREMENT BY 1 START WITH 3467 NOCACHE NOORDER NOCYCLE ;
每当我使用序列名称id_seq2的以下序列生成器触发邮递员的任何服务时,我都会收到错误“序列不存在”。但是,序列已经存在于DB中
@GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "id_generator")
@SequenceGenerator(name="id_generator", sequenceName = "id_seq2", allocationSize=1)
private Long transactionId;
项目war文件已成功部署到服务器上。之后,无论何时从邮递员触发服务,都会发生以下错误:
org.hibernate.exception.SQLGrammarException: could not extract ResultSet
at org.hibernate.exception.internal.SQLExceptionTypeDelegate.convert(SQLExceptionTypeDelegate.java:82)
at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:49)
at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:124)
at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:109)
at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.extract(ResultSetReturnImpl.java:88)
at org.hibernate.id.SequenceGenerator.generateHolder(SequenceGenerator.java:122)
at org.hibernate.id.SequenceHiLoGenerator.generate(SequenceHiLoGenerator.java:73)
at org.hibernate.event.internal.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:117)
at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSaveOrUpdateEventListener.java:206)
at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEventListener.java:191)
at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:114)
at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:90)
at org.hibernate.internal.SessionImpl.fireSaveOrUpdate(SessionImpl.java:654)
at org.hibernate.internal.SessionImpl.saveOrUpdate(SessionImpl.java:646)
at org.hibernate.internal.SessionImpl.saveOrUpdate(SessionImpl.java:642)
at com.etisalat.mwallet.data.BaseDAO.save(BaseDAO.java:49)
at com.etisalat.mwallet.service.impl.LoggerService.logFrontEnd(LoggerService.java:59)
at com.etisalat.mwallet.service.impl.LoggerService.logFrontEndSuccess(LoggerService.java:29)
at com.etisalat.mwallet.rest.config.ResponseFilter.doFilter(ResponseFilter.java:180)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3436)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3402)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)
at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2285)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2201)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1572)
at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:255)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)
Caused by: java.sql.SQLSyntaxErrorException: ORA-02289: sequence does not exist
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1059)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:522)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:257)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:587)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:225)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:53)
at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:774)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:925)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1111)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:4798)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:4845)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1501)
at weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:141)
at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.extract(ResultSetReturnImpl.java:79)
案例2:
CREATE SEQUENCE "id_seq2" MINVALUE 0 MAXVALUE 9999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ;
commit;
CREATE SEQUENCE "id_seq1" MINVALUE 0 MAXVALUE 9999999999999999999999999999 INCREMENT BY 1 START WITH 3467 NOCACHE NOORDER NOCYCLE ;
之后为了测试目的,我将序列名从id_seq2更改为id_seq1,并在服务器上重新部署了代码,令人惊讶的是,我能够成功地触发服务
@GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "id_generator")
@SequenceGenerator(name="id_generator", sequenceName = "id_seq1", allocationSize=1)
private Long transactionId;
输出:
{
响应代码:“0”
}
我不知道我在哪里犯了错误,因为在我看来,在sequence generator中我遗漏了一些东西。在您的情况下,序列必须与您登录的架构/用户存在于同一架构中。如果您以其他用户的身份登录,那么您可以尝试这种相当粗鲁的解决方案
create public synonym "id_seq2" for "id_seq2";
grant select on "id_seq2" to public;
或者尝试找出“id_seq1”中的priv和同义词,并将其应用到“id_seq2”中。存在的缺失序列可能是由两个原因造成的:
1) 序列存在于与之连接的其他架构中
在这种情况下,您必须引用schema\u owner
schema\u name
2) 序列存在于不同的架构中,您没有访问它的权限
您应该首先了解现有序列是在哪个模式中创建的
您可以通过以下查询进行验证(根据需要替换序列名称)
如果未看到任何内容,则序列不存在,或者它存在于您所连接的其他架构中,并且您没有SELECT
权限
如果您使用的序列来自与Hibernate连接用户不同的模式(这是一种非常常见的情况),则必须使用
@SequenceGenerator
注释的参数并传递propper模式所有者。它是否在正确的模式中,DB用户是否看到序列,它是否在正确的表空间中。。。首先要弄清楚这一点。是的,它属于正确的方案和序列。两个序列的所有者也与“AAK”相同。只需注意:最大值为10^28-1,约为2^84,因此不适合长(2^63)。通常在Oracle中,您不会给对象强制使用小写名称。可能Spring正在生成一个对id\u seq2
的引用,该引用不存在,因为您实际创建了“id\u seq2”
。(这可能不是问题,因为它似乎适用于“id_seq1”
,但这确实是一个您不需要的复杂问题。)上帝禁止在命名Oracle对象时使用双引号!同意,但它在示例中,如果它在create语句中,您最好继续:)很遗憾,是的。我应该把这个评论放在问题下面(这样更有意义)。