New answers tagged

0

You can't use utl_file, since it has a maximum line length of 32767. It's possible that sqlplus has a similar limit. If you are tying to move data to a different Oracle database you can use data pump. You can eve use datapump on a materialized view. If you want to migrate to a non Oracle database you can use Perl or heterogeneous services to create a ...


0

This worked for me: alter role postgres password '';


0

I figured out a solution. The key to this solution is that I already had a system (the master) that I knew I could generate the timezone SQL on. I simply generated the SQL on the master, transferred it to the slave, and executed it! On Master user@master [~]# mysql_tzinfo_to_sql /usr/share/zoneinfo/ > timezones.sql On Slave root@slave:~# scp -P2223 ...


0

As dezso mentioned in the question comments, this did seem to be an issue with (possibly more recent versions of the) 3.13 kernel in Ubuntu Trusty - we switched to the Xenial HWE 4.4 kernel in Trusty and the problem seems to have gone away and compaction stalls are now very small and don't interfere.


4

there's a space missing before to in 'to myuser'. BEGIN FOR X in (select * from all_tables where owner in ('TESTDTA', 'TESTCTL')) LOOP EXECUTE IMMEDIATE 'GRANT SELECT, INSERT, UPDATE, DELETE ON ' ||X.owner||'.'||X.table_name|| ' to TESTUSER'; END LOOP; END; /


0

If you have set a time zone for your Postgres DB cluster in postgresql.conf, changing the time zone of the server OS will have no bearing on your databases at all - as long as you don't actually change the time itself, not just the time zone. You need to make sure that none of your client programs feed local time to the database, which would actually change ...


-1

File in etc/my.cnf Find this # The MySQL server [mysqld] and set lower_case_table_names = 1 There is no need to drop db. It works so first check with this. Reason is default value of lower_case_table_names =1 for Windows.


0

Had a similar issue, myself, where my app could connect from Visual Studio, but not when published to a server. Nothing here resolved it for me, though zaratustra's post helped, but so I thought I'd link to my post - ORA-01017: invalid username/password;logon denied - to show how to troubleshoot these - or at least, how I did, before I gave up and posted my ...



Top 50 recent answers are included