Thursday, October 28, 2021

[google-cloud-sql-discuss] Unable to Demote SQL Cloud Master to act as Slave

I have a SQL Cloud which was working as Slave and then the replication was broken and to resync It is must to import and then demote. 

I can't demote after importing.

Thank you for your support in advance

Shazad Saleem

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/1a288d32-8195-49db-8a2a-cf702976ce4en%40googlegroups.com.

Monday, October 18, 2021

[google-cloud-sql-discuss] Re: Oracle OnPremise - Cloud Data Fusion

Hello,

Since the issue you're describing seems to require the product engineering team to review it and likely reproduce it, the best approach would be for you to describe and file a public issue using this Issue Tracker topic template [1], and the Support Team will handle it appropriately from there. Also, for future issues you encounter when using Cloud Data Fusion, apart from the Issue Tracker template provided, I believe this Google Groups thread [2] could also be more helpful for your issues than the threads used for this current issue.

Best regards,
Bernat

[2]: https://groups.google.com/g/cdap-user

On Friday, October 15, 2021 at 10:05:45 AM UTC+2 franz....@xertica.com wrote:
Our Oracle data source is hosted in On-Premises server. We already set the VPC communication channel between Oracle and Google Cloud and using a Oracle credentials we can also watch the some Oracle tables from objects preview section in Cloud Data Fusion (cDF).

We can access to consume only the Oracle tables which are using SYNONYMS. The problem is with remaining tables, which are using schema, for instance SCHEMA_NAME.TABLE_NAME, without use synonyms, we can not access from cDF, neither even to valide in Preview environment.

¿Is that an issue of cDF? ¿How can I solve it? and to consume also the tables which are using schema's sintaxis. Please your help and guidance.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/0d6d06e5-7905-4da0-abe9-0c61091e7b59n%40googlegroups.com.

Thursday, October 14, 2021

[google-cloud-sql-discuss] Oracle OnPremise - Cloud Data Fusion

Our Oracle data source is hosted in On-Premises server. We already set the VPC communication channel between Oracle and Google Cloud and using a Oracle credentials we can also watch the some Oracle tables from objects preview section in Cloud Data Fusion (cDF).

We can access to consume only the Oracle tables which are using SYNONYMS. The problem is with remaining tables, which are using schema, for instance SCHEMA_NAME.TABLE_NAME, without use synonyms, we can not access from cDF, neither even to valide in Preview environment.

¿Is that an issue of cDF? ¿How can I solve it? and to consume also the tables which are using schema's sintaxis. Please your help and guidance.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/a6f72319-c345-4b20-aacd-11a11b2989bfn%40googlegroups.com.

Wednesday, October 13, 2021

Re: [google-cloud-sql-discuss] Re: How do I work around MySQL Bug #69721 (Block Nested Loop making things slower)

Hi,

We are facing this issue as well and it impacts our business, the only solution we have now is to move our databases to AWS, there should be a workaround for this at least from Google.

On Sunday, May 23, 2021 at 8:45:43 PM UTC+2 yananc wrote:

Hi, 

As seen on the public issue and the internal one, the feature for setting optimizer-switch=block_nested_loop=off is still under the evaluation of the Cloud SQL Engineering team. Please kindly note that there is no ETA or guarantee on the implementation. Thank you.

On Sunday, May 16, 2021 at 5:49:59 PM UTC-4 feja...@gmail.com wrote:
Hi,

Please how were you able to resolve this eventually, I am also stuck in the same situation.

Thanks

On Thursday, 4 April 2019 at 08:53:38 UTC+1 krzysz...@gmail.com wrote:
Thanks, I issued https://issuetracker.google.com/issues/129897196

On Thu, Apr 4, 2019 at 1:57 AM 'Harmit Rishi (Cloud Platform Support)'
via Google Cloud SQL discuss
<google-cloud...@googlegroups.com> wrote:
>
> Thank you for using Google Groups.
>
>
> Considering that Cloud SQL offers MySQL instances, I believe this issue should be brought to the attention of the engineering team behind the Cloud SQL product. Due to this, I encourage you to follow the steps to file a Public Issue Tracker here[1].
>
>
> Also, doing so will ensure that this issue is getting the appropriate exposure to the engineering team as Google Groups is meant for discussion purposes. Let me know if you are able to file a Public Issue Tracker for this.
>
>
> [1] Public Issue Tracker: https://cloud.google.com/support/docs/issue-trackers
>
> On Wednesday, February 27, 2019 at 2:26:49 PM UTC-5, Krzysztof Drys wrote:
>>
>> Recently we experienced problems with our MySQL instance. One hour our db was running fine (CPU usage at about 20%), next hour CPU is at 100% and queries are stuck at "creating sort index" phase. After restarting DB everything was normal again.
>>
>> We suspect that it was MySQL Bug #69721 (https://bugs.mysql.com/bug.php?id=69721). As suggested here (https://community.sugarcrm.com/thread/33079-queries-getting-stuck-on-creating-sort-index-slowing-sugar-down), one option to mitigate this bug is to set optimizer-switch=block_nested_loop=off.
>>
>> However, as far as I can see, it is not possible to set this option in Cloud MySQL. Do you know any other way to work around this bug?
>>
>> Thanks,
>> Krzysztof Dryƛ
>
> --
> You received this message because you are subscribed to a topic in the Google Groups "Google Cloud SQL discuss" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-cloud-sql-discuss/cPeyrQ4Rbz0/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to google-cloud-sql-d...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/68475f91-8f40-4dbb-80ff-64e76e5f0dc0%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/949d14e7-b4c3-464f-b640-2630dd7c77dcn%40googlegroups.com.

Wednesday, October 6, 2021

[google-cloud-sql-discuss] storage/speckle/postgres/extensions/google_insights/google_insights.c:1102: Unable to report sampled query plan

After enabling Query Insights, our Cloud SQL Postgres logs are full of logs like this:

"LOG: storage/speckle/postgres/extensions/google_insights/google_insights.c:1102: Unable to report sampled query plan for SELECT xxx due to hashtable size limit"

How do I fix this? It's very spammy, makes it hard to find useful logs, and seems to indicate that some portion of our database's queries are not actually being tracked by Query Insights. Would increasing the query length for Query Insights fix this?

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/259747e8-ae31-44c9-a83f-ade417114c91n%40googlegroups.com.

Monday, October 4, 2021

[google-cloud-sql-discuss] Re: Cloud SQL private IP access via VPN Tunneling

Hi,
Please make sure to use Cloud VPN with Dynamic routing (BGP).

On Wednesday, July 1, 2020 at 2:26:08 AM UTC+7 Agam Bajwa wrote:
I have two projects 1 and 2 and two vpc networks vpc1 and vpc2 in the respective projects. I need to connect to sql instance in vpc2 (project2) from vm in vpc1 project1 using private IP. After trying diiferent methods and exploring options like vpc peering, cloud NAT (which wouldn't work for me) I found the cloud VPN solution. I am following this google docs link - https://cloud.google.com/sql/docs/postgres/configure-private-ip#vpn to connect to cloudSQL instance using its private IP. I have setup VPN Tunneling and all the necessary steps that were mentioned in the steps 1 and 2 in the link itself, but not able to connect to the instance. I have tested the VPN connectivity as well. I am able to ping a vm2 in vpc2 (project2) from vm1 in vpc1 (project1).

I suspect the problem is in the final steps over here:
https://i.stack.imgur.com/aIyq8.png

No problem in step a and step b is also clear, but what exactly needs to be done in step c is not clear. Can you explain what needs to be done over there.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/dac74066-c357-418d-9a67-68f308a96644n%40googlegroups.com.

Sunday, October 3, 2021

[google-cloud-sql-discuss] Re: How to Connect Google SQL database from AWS EC2

Hi,
VPN should be using BGP with dynamic route.  Then you need config export custom route in cloudsql peering vpc.
https://cloud.google.com/sql/docs/mysql/configure-private-ip#vpn 

On Monday, August 30, 2021 at 2:09:30 PM UTC+7 kazea...@gmail.com wrote:
Hello, i'm new member here, i have a problem for connecting my Cloud SQL DB from AWS Ec2, now i have VPN S2S between AWS and GCP and it's now already work for ping and remote vm each other, but when i want to connect database from AWS EC2 always fail and can't connect with error "ERROR 2003 (HY000): Can't connect to MySQL server on '10.xx.xx.xx' (110)" what must be to do?

thanks

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/188d448c-e94a-4ca5-a4f3-be6986c312e0n%40googlegroups.com.

Friday, October 1, 2021

[google-cloud-sql-discuss] Re: Upgrade GCP hosted PostgreSQL while keeping existing user passwords

My database for Lil Peep's rare merch suffers from the same problem. I have read all documentation, but cannot resolve the issue.

On Wednesday, 1 September 2021 at 12:37:09 UTC+5 jo...@vendohm.com wrote:
I have been tasked with upgrading our existing GCP hosted PostgreSQL databases from version 9.6 to version 13.

say that we need to create a new database and then
"Make sure the target instance has... The same user accounts, with the same PostgreSQL privileges and passwords"

We have a number of databases with dozens of users and roles, we allow users to connect directly and set their own passwords.
We would like to perform the database upgrade without changing all the passwords.

I've looked at using pg_dumpall to copy the users to a new database, but it fails as I don't have permission to read pg_authid.
It seems that we need a superuser account to be able to read pg_authid, and GCP does not permit superuser accounts.

Is there any way to upgrade the databases and keep the existing passwords?

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/3f7b368c-4e5f-4179-a43d-2db52258148fn%40googlegroups.com.