Loading...
Loading...
Replication failures like: - Slow replication alarm - Nodes getting out of sync randomly
Use command: "show logging application replication.log | include Overflow" api.services.persistance.dao.ChangeDataDaoImpl -::::- Exception occured in getBySequence(2180751507,2180751516) method java.sql.SQLException: Numeric Overflow at oracle.jdbc.driver.NumberCommonAccessor.throwOverflow(NumberCommonAccessor.java:4139) at oracle.jdbc.driver.NumberCommonAccessor.getInt(NumberCommonAccessor.java:125) at oracle.jdbc.driver.GeneratedStatement.getInt(GeneratedStatement.java:199) at oracle.jdbc.driver.GeneratedScrollableResultSet.getInt(GeneratedScrollableResultSet.java:246) at oracle.jdbc.driver.GeneratedResultSet.getInt(GeneratedResultSet.java:556)
reset-config can help as it will purge the database. However, this will be time consuming. Contact TAC to truncate the table manually
NA
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.