a11dev opened a new issue, #6662:
URL: https://github.com/apache/seatunnel/issues/6662

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22)
 and found no similar issues.
   
   
   ### What happened
   
   seatunnel 2.3.4 
   windows server local environment deployment 
   openjdk version "21.0.2" 2024-01-16
   oracle database ( dbaas ) 
   local postgres 
   3 oracle table - OracleCDC
   3 Sink - jdbc 
   
   It crash with an ORA-01292 
   
[seatunnellog.zip](https://github.com/apache/seatunnel/files/14903517/seatunnellog.zip)
   
   All logs ( and config example ) attacched.
   
   I can increase log level if necessary.
   
   Might it be related to an automatic backup of redologs?
   [config.zip](https://github.com/apache/seatunnel/files/14903592/config.zip)
   
   ### SeaTunnel Version
   
   2.3.4
   
   ### SeaTunnel Config
   
   ```conf
   #Also into the first attachment:
   
   
   env {
        parallelism = 2
       job.mode=STREAMING
       job.name=SeaTunnel_Job
       read_limit.bytes_per_second=7000000
       read_limit.rows_per_second=400
   }
   
     Oracle-CDC {
   
       result_table_name = "tab1"
       base-url = "jdbc:oracle:thin:user/password@ip:1521/service_name"
       source.reader.close.timeout = 120000
       username = "user"
       password = "password"
       database-names = ["DBNAME"]
        # real db name DBNAME.domain.local ( it works with DBNAME )
       schema-names = ["SCHEMA"]
       startup.mode = "INITIAL"
       table-names = ["DBNAME.SCHEMA.TABLE1"]
     }
   
   
   }
   
   
   sink {
       jdbc {
                source_table_name="tab1"
                url = "jdbc:postgresql://localhost:5432/pgdatabase"
                driver = "org.postgresql.Driver"
                user = pguser
                password = pgpassword
                generate_sink_sql = true
                database = pgdatabase
                table = public.tab1
                primary_keys = ["PKNAME"]
                field_ide = LOWERCASE,
                schema_save_mode = "CREATE_SCHEMA_WHEN_NOT_EXIST"
                data_save_mode="APPEND_DATA"
       }
   
   }
   ```
   
   
   ### Running Command
   
   ```shell
   java 
-Dlog4j2.configurationFile=E:\programmi\apache-seatunnel-2.3.4\config\log4j2_client.properties
 
-Dhazelcast.client.config=E:\programmi\apache-seatunnel-2.3.4\config\hazelcast-client.yaml
 -Dseatunnel.config=E:\programmi\apache-seatunnel-2.3.4\config\seatunnel.yaml 
-Dhazelcast.config=E:\programmi\apache-seatunnel-2.3.4\config\hazelcast.yaml 
-Dseatunnel.logs.file_name=seatunnel-starter-clienttest -Xms256m -Xmx512m 
-XX:+HeapDumpOnOutOfMemoryError 
-XX:HeapDumpPath=E:\programmi\apache-seatunnel-2.3.4\dump\zeta-client  -cp 
E:\programmi\apache-seatunnel-2.3.4\lib\*;E:\programmi\apache-seatunnel-2.3.4\starter\seatunnel-starter.jar
 org.apache.seatunnel.core.starter.seatunnel.SeaTunnelClient  --config 
.\config\v2.batch.config.template -m local
   ```
   
   
   ### Error Exception
   
   ```log
   2024-04-06 14:35:03,888 ERROR [i.d.c.o.l.LogMinerHelper      ] 
[debezium-reader-0] - Mining session stopped due to the java.sql.SQLException: 
ORA-01291: file di log mancante
   ORA-16241: In attesa del file di log dell'intervallo (n. thread 2, n. 
sequenza 106896)
   
   
   
   // into the first attachment
   ```
   
   
   ### Zeta or Flink or Spark Version
   
   Zeta
   
   ### Java or Scala Version
   
   openjdk version "21.0.2" 2024-01-16
   
   ### Screenshots
   
   everything is inside attachements.
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to